#998: CSS Selectors 4; :local-link

Visit on Github.

Opened Sep 30, 2024

こんにちは TAG-さん!

I'm requesting a TAG review of the :local-link pseudo class.

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.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: I'll be working on prototypes for browsers this week.
  • The group where the work on this specification is currently being done: CSSWG
  • The group where standardization of this work is intended to be done (if different from the current group): CSSWG
  • Major unresolved issues with or opposition to this specification: None
  • This work is being funded by: Me, or I guess GitHub, but they allow me to contribute as an independant.

You should also know that...

I'll be implementing a prototype this week in Chrome/Firefox/WebKit.

Discussions

Comment by @jyasskin Sep 30, 2024 (See Github)

Thanks! My personal review is in https://github.com/w3c/csswg-drafts/issues/10975, but that's not the full TAG's opinion. The use case, at least, seems great.

Comment by @LeaVerou Sep 30, 2024 (See Github)

Agree with @jyasskin about the name, but the use case is a huge pain point. It is very nontrivial to implement with JS, and comes up in literally every navigation menu. The lack of this made teaching web technologies significantly harder.

Discussed Oct 14, 2024 (See Github)

This name is confusing, but apparently not everyone thinks that.

We'll discuss in Plenary: should Jeffrey's issue be "promoted" to coming from the TAG and not just himself? (Everyone present in this breakout believes we should.)

Comment by @jyasskin Oct 17, 2024 (See Github)

The TAG discussed this as a whole and agreed that we're enthusiastic about the use case being solved, and want it to be solved with more precise names. Thank you!