[w3ctag/design-reviews] Other Spec Review: Add keyword "pair" to scroll-snap-type for snapping to the same element in X and Y axes (Issue #1271)

lcdavid94 created an issue (w3ctag/design-reviews#1271)

### Specification

https://github.com/w3c/csswg-drafts/pull/14386

### Explainer

https://github.com/explainers-by-googlers/scroll-snap-type-pair

### Links

- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/explainers-by-googlers/scroll-snap-type-pair
- A description of the problems that end-users were facing before this proposal: When "scroll-snap-type: both" is specified, the scroll container searches for snap points on X and Y axes independently. https://github.com/w3c/csswg-drafts/issues/9519
- Examples of how to use the proposal to solve the end-users' problems: https://github.com/explainers-by-googlers/scroll-snap-type-pair#use-case-2d-interactive-map-with-points-of-interest-demo
- What do the end-users experience with this proposal: https://github.com/explainers-by-googlers/scroll-snap-type-pair#proposal
- Web Platform Tests:  Tentative test for parser: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/css/css-scroll-snap/pair/scroll-snap-type-pair.tentative.html Will add more tests.


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/csswg-drafts/
- Primary contacts:
 - David Liu (@lcdavid94), Google, Author
 - Robert Flack (@flackr), Google, Spec work & reviewer
 - Vladimir Levin (@vmpstr), Google, Reviewer
- Organization/project driving the specification: Google
- This work is being funded by: Google
- Primary standards group developing this feature: CSSWG
- Incubation and standards groups that have discussed the design:
 - https://github.com/w3c/csswg-drafts/issues/9519

### Feedback so far

- Multi-stakeholder feedback:
  - Chromium comments: https://chromestatus.com/feature/5124378896498688
  - Mozilla comments: https://github.com/mozilla/standards-positions/issues/1448
  - WebKit comments: https://github.com/WebKit/standards-positions/issues/716
- Major unresolved issues with or opposition to this specification:
- Status/issue trackers for implementations: Chromium comments: https://chromestatus.com/feature/5124378896498688


### You should also know that...

_No response_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1271


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

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