Re: [w3ctag/design-reviews] Soft Navigations (Issue #879)

One missing condition in my previous clarification (now fixed) is that the keypress is unfocused (i.e. its target is the body element). So a tab key that changes focus would not be considered for a soft navigation, but e.g. a tab key that is used to move between different pages would be.



> > * In case of a “click” or a keyboard event, the handler triggered tasks that included `history.pushState()` or `history.replaceState()` calls, or a change to the document’s location.
> 
> But then where does the contentful paint come in?

For a soft navigation to be detected, an eligible event ("click" or unfocused keyboard event) would need to spawn tasks that both change the URL *and* append DOM nodes that end up with contentful paints.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/879#issuecomment-1831268377
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/879/1831268377@github.com>