- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 17:01:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-scroll-snap-1] Improve or clarify nested snap behaviors`. <details><summary>The full IRC log of that discussion</summary> <fantasai> flackr: We've had many devs trying to use scroll-snap reach out to us regarding differen thing sthey're trying to build<br> <fantasai> flackr: one common use case is nesting snap areas to have a large area you can scroll freely, and some mandatory areas<br> <fantasai> flackr: paginated view within larger scroller<br> <fantasai> flackr: the spec suggests that this should be supported<br> <fantasai> flackr: but normative text doesn't explicitly define the expected outcome<br> <fantasai> flackr: so wanted to get feedback on this proposal to add explicit text<br> <fantasai> flackr: when yu're in overly large snap area, should avoid inter-snap areas<br> <fantasai> flackr: this creates desired effect of screens within a larger snap area<br> <fantasai> flackr: you either fully snap into view or avoid them<br> <fantasai> flackr: so proposal for change<br> <fantasai> flackr: a few cases to discuss, what do you do if those inter-snap areas aren't screen sized<br> <fantasai> flackr: not want to introduce large jumps in scroll because of single-line snap area<br> <fantasai> flackr: but I think we can define reasonable behaviors<br> <fantasai> flackr: do we think this is reasonable to put in the spec?<br> <fantasai> flackr: I can propose spec text, and have examples and diagrams<br> <fantasai> Rossen_: Thanks for intro, indeed the diagrams in the issue and spec are making this very visual and easy to follow<br> <fantasai> Rossen_: not seeing anyone in the queue, if interested in topic engage in issue and perhaps can return later<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9187#issuecomment-1758117230 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 17:01:28 UTC