[w3ctag/design-reviews] Specification review for CSS Anchor Positioning (Issue #848)

こんにちは TAG-さん!

I'm requesting a TAG review of CSS Anchor Positioning.

[CSS Anchor positioning](https://drafts.csswg.org/css-anchor-position-1/) is a CSS feature that allows an element to position and size itself relative to one or more "anchor elements" elsewhere on the page. A typical use case is to "pin" a tooltip to something that triggers it.

  - Explainer¹ (minimally containing user needs and example code): https://xiaochengh.github.io/Explainers/css-anchor-position/explainer.html
  - Specification URL: https://drafts.csswg.org/css-anchor-position-1/
  - Tests: https://wpt.fyi/results/css/css-anchor-position
  - Security and Privacy self-review: see below
  - User research: none
  - Primary contacts (and their relationship to the specification):
      - [Xiaocheng Hu] (@xiaochengh), Google, Chromium implementor, explainer author
      - [Tab Atkins] (@tabatkins), Google, spec editor
  - Organization(s)/project(s) driving the specification: CSSWG
  - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/w3c/csswg-drafts/issues/7282#issuecomment-1249591201
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5124922471874560

Security and Privacy self-review:

```
2.1. What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?
No additional information.
2.2. Do features in your specification expose the minimum amount of information necessary to enable their intended uses?
Yes.
2.3. How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?
No PII.
2.4. How do the features in your specification deal with sensitive information?
No change.
2.5. Do the features in your specification introduce new state for an origin that persists across browsing sessions?
No.
2.6. Do the features in your specification expose information about the underlying platform to origins?
No.
2.7. Does this specification allow an origin to send data to the underlying platform?
No.
2.8. Do features in this specification enable access to device sensors?
No.
2.9. Do features in this specification enable new script execution/loading mechanisms?
No.
2.10. Do features in this specification allow an origin to access other devices?
No.
2.11. Do features in this specification allow an origin some measure of control over a user agent’s native UI?
No.
2.12. What temporary identifiers do the features in this specification create or expose to the web?
None.
2.13. How does this specification distinguish between behavior in first-party and third-party contexts?
No change from existing behavior.
2.14. How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?
No change from existing behavior.
2.15. Does this specification have both "Security Considerations" and "Privacy Considerations" sections?
Yes.
2.16. Do features in your specification enable origins to downgrade default security protections?
No.
2.17. How does your feature handle non-"fully active" documents?
No change from existing behavior.
2.18. What should this questionnaire have asked?
Not expecting any.
```

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: June 16, 2023
  - The group where the work on this specification is currently being done: CSSWG
  - Major unresolved issues with or opposition to this specification: none
  - This work is being funded by: Google

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @xiaochengh


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

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