- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 20:02:48 +0000
- To: public-css-archive@w3.org
> jump is everything else (traversing more than +-1 back/forward, or navigating via URL bar etc) The idea sounds nice but its unfortunate that navigation type in CSS will diverge from [navigation type](https://developer.mozilla.org/en-US/docs/Web/API/NavigateEvent/navigationType) in JS defined by the navigation API. This might be inevitable if we can't change the JS navigation type in a backwards compatible way but worth trying to keep these consistent to the extent possible. @domenic @natechapin FYI. Could we organize the CSS navigation types as sub-types of the JS versions? - push: Needs 2 sub-types to distinguish page initiated (expected transitions) and browser UI initiated (unexpected transitions). - reload: Works as-is. - replace: Works as-is. - traverse: Needs sub-types for back/forward and one to distinguish more than 1 offset traversal aka jump. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1756140646 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 20:02:50 UTC