- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jun 2024 15:06:48 +0000
- To: public-css-archive@w3.org
> Do I understand correctly that this would require navigation.activation.from to be populated in the cross-origin-but-same-site case? Yes, the Document would need this information to customize the transition. > I think that's probably doable if both origins consent to it, but it would be important to note that some of the information on navigation.activation.from would be incomplete or unusuable. Most notably, a from.key would be rejected if given to navigation.traverseTo, and from.index would always be -1. Can you expand on this a bit more? My thinking was that an opt-in from 2 same-site cross-origin URLs means we can expose all the information that is provided by the navigation API to same-origin URLs. Is there a reason we shouldn't do that? And specifically about your comment for `traverseTo`, do you think this opt-in should only provide readonly state but not allow authors to do actions provided by the navigation API..? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10364#issuecomment-2176338393 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 June 2024 15:06:49 UTC