- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 16:41:36 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-scroll-snap] Difficult to use snap areas which are larger than the scrollport`, and agreed to the following: * `RESOLVED: any postion within the overlarge snap area is a valid snap position, as defined in the (clarified) spec` <details><summary>The full IRC log of that discussion</summary> <fantasai> flackr: fantasai and Tab both commented that the intention is what I am asking for<br> <fantasai> flackr: [describes issue]<br> <fantasai> flackr: I'm seeing a lot of support for that sentiment in the issue<br> <fantasai> flackr: I think we're resolving that the updated spec is good, with expected behavior<br> <fantasai> [reviewing the comments in the issue]<br> <fantasai> fantasai: Tab's comment isn't correct, intention of spec was that any position within the overlarge snap area would be a valid place to rest<br> <fantasai> current spec -> https://drafts.csswg.org/css-scroll-snap-1/#snap-overflow<br> <fantasai> flackr: I think the current spec is good<br> <fantasai> PROPOSED: any postion within the overlarge snap area is a valid snap position, as defined in the (clarified) spec<br> <fantasai> RESOLVED: any postion within the overlarge snap area is a valid snap position, as defined in the (clarified) spec<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6863#issuecomment-1854300040 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 16:41:38 UTC