- From: Noam Rosenthal via GitHub <noreply@w3.org>
- Date: Wed, 03 Sep 2025 19:56:29 +0000
- To: public-css-archive@w3.org
Thinking the following: - I don't yet see a point in generalizing `sourceElement`'s behavior with form. Do you ever need to style a form that is the source of a navigation in the same way you'd style a link that is the source of the navigation? - Staying with links here, there are two possible links: the one that *actually* triggered the navigation, and one or more that *match* the remote navigation URL. Given that, I think we can stay with the `*-link` pseudo-classes, and have: - `:remote-link` - the counterpart of `:local-link`, selects the "non-current" URL in a navigation. Will work symmetrically for back navigations. - `:trigger-link` or `:active-link` or `:source-link`: a link that *actually* triggered this navigation - Both of these would only work *during* a navigation: from the point a navigation is initiated until the navigation handlers are done (and the navigation-triggered view-transition is finished, if exists). - In addition see #12594 for how this works with the concept of routes, where the URL matching doesn't have to be 1:1. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11801#issuecomment-3250576566 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 September 2025 19:56:30 UTC