You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigate a possible Exit this Page feature to create a "ghost page" the screen upon button activation before navigating to the next page aka: when the user clicks the button, the screen immediately goes white and then navigates to a new page.
This is a feature idea that emerged following the analysis of the Exit this Page research. The idea being that users on slow connections won't have the contents of the page they are leaving on their screen whilst the button handles navigation.
The team are mostly confident about this idea as an enhancement, but there are some unknowns:
Does the ghost page need some text?
Does the ghost page need a visual progress indicator of loading such as a spinner?
Would the ghost page functionality still work if the button was treated like a normal link and we didn't block standard functionality using e.preventDefault?
What are the risks of the ghost page functionality breaking and leaving the user with a screen they can't interact with?
Who needs to work on this
Developers, Designers, Accessibility specialists
Done when
Investigate ghost page feature implementation and write up findings/proposals
Implement proposals, if any
The text was updated successfully, but these errors were encountered:
What
Investigate a possible Exit this Page feature to create a "ghost page" the screen upon button activation before navigating to the next page aka: when the user clicks the button, the screen immediately goes white and then navigates to a new page.
Part of #1755
Time limit: 1 week
Why
This is a feature idea that emerged following the analysis of the Exit this Page research. The idea being that users on slow connections won't have the contents of the page they are leaving on their screen whilst the button handles navigation.
The team are mostly confident about this idea as an enhancement, but there are some unknowns:
e.preventDefault
?Who needs to work on this
Developers, Designers, Accessibility specialists
Done when
The text was updated successfully, but these errors were encountered: