[w3ctag/design-reviews] CSS Selectors 4; :local-link (Issue #998)

こんにちは TAG-さん!

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

The :local-link pseudo-class allows authors to style [hyperlinks](https://drafts.csswg.org/selectors-4/#the-any-link-pseudo) 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.

  - Explainer¹: https://drafts.csswg.org/selectors-4/#the-local-link-pseudo
  - Specification: https://drafts.csswg.org/selectors-4/#the-local-link-pseudo
  - WPT Tests: (Not yet, will live in https://github.com/web-platform-tests/wpt/tree/master/css/selectors)
  - User research:
  - Security and Privacy self-review²:
  - GitHub repo:
  - Primary contacts:
      - Keith Cirkel (@keithamus), Microsoft/GitHub, Implementer
      - Lea Verou (@LeaVerou), Font Awesome, CSSWG Invited Expert
      - (@fantasai), Apple, CSSWG Spec writer
  - Organization/project driving the specification: Already specified
  - Multi-stakeholder support³:
    - Chromium comments:
    - Mozilla comments: https://github.com/mozilla/standards-positions/issues/862
    - WebKit comments: https://github.com/WebKit/standards-positions/issues/405
    - {{...include feedback/review from developers, implementers, civil society, and others}}
  - Status/issue trackers for implementations⁴:

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/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...

{{Please tell us anything else you think is relevant to this review.}}

------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Use links to content rather than pasting text into this issue. Issues are ephemeral and most of the material we are asking for has long term value.

Please preview the issue and check that the links work before submitting. Please make sure anyone with the link can access the document. We may refuse to review anything that is not public.

¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. An explainer must address user needs and contain examples of use.  For more information, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/).

² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.

³ For your own organization, you can simply state the organization's position instead of linking to it.  This includes items on [Mozilla standards-positions](https://github.com/mozilla/standards-positions), and [WebKit standards-positions](https://github.com/WebKit/standards-positions).  Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase.

⁴ Include links to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), and trackers for other implementations if those are known to you.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/998
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/998@github.com>