> If the hyperlink’s target includes a fragment URL, then the fragment URL
of the current URL must also match
That sounds strange and less desired to me, as even if it has a fragment,
it is still on the same page. But maybe the use case is using the fragment
part for navigation in a single page application? I have seen that being
used less and less.

☆*PhistucK*


On Mon, Sep 30, 2024 at 12:40 PM Keith Cirkel <chrom...@keithcirkel.co.uk>
wrote:

> Contact emails
> chrom...@keithcirkel.co.uk
>
> Explainer
> https://drafts.csswg.org/selectors/#local-link-pseudo
>
> Specification
> https://drafts.csswg.org/selectors/#local-link-pseudo
>
> Summary
>
> The :local-link pseudo-class allows authors to style hyperlinks based on
> the users current location within a site. It represents an element that is
> the source anchor of a hyperlink whose target’s absolute URL matches the
> element’s own document URL. If the hyperlink’s target includes a fragment
> URL, then the fragment URL of the current URL must also match; if it does
> not, then the fragment URL portion of the current URL is not taken into
> account in the comparison.
>
> Blink component
> Blink>CSS
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM>
>
> Motivation
>
> It's common to style the active page in a list of links differently the
> others to denote the user is on such a page. This typically requires
> maintaining such state in the host language, such as the server side
> template language, or in the client. `:local-link` provides a browser
> built-in solution to this.
>
> Initial public proposal
> https://drafts.csswg.org/selectors/#local-link-pseudo
>
> TAG review
> None
>
> TAG review status
> Pending
>
> Risks
>
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: No signal
>
> *WebKit*: No signal
>
> *Web developers*: Positive
>
> *Other signals*:
>
> WebView application risks
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
>
> None
>
>
> Debuggability
>
> None
>
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?
> No
>
> Flag name on chrome://flags
> Experimental Web Platform Features
>
> Finch feature name
> None
>
> Non-finch justification
> None
>
> Requires code in //chrome?
> False
>
> Estimated milestones
>
> No milestones specified
>
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5194826811965440
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ad994a5a-8966-449d-a0e1-2f46086e4bc2%40app.fastmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ad994a5a-8966-449d-a0e1-2f46086e4bc2%40app.fastmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_KRG%2BLYkFqsaZO-H2mBn1W8c4pHBqtXPLoWq0GtuEKQPQ%40mail.gmail.com.

Reply via email to