Dated Draft:https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/
Editor's Draft:http://drafts.csswg.org/css-scroll-snap-1/
The following color coding convention is used for comments:
Open issues are marked like this
An issue can be closed asAccepted,OutOfScope,
Invalid,Rejected,orRetracted.
Verifiedindicates commentor's acceptance of the response.
Issue 1.# Summary: Examples and syntax of scroll-snap-type conflict From: Wenson Hsieh Comment:https://github.com/w3c/csswg-drafts/issues/827 Response:https://github.com/w3c/csswg-drafts/issues/827#issuecomment-269347510 Changes:https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76 Closed: Accepted Resolved: Editorial
Issue 2.# Summary: Clarify that css-scroll-snap doesn't dictate any particular input method From: Benoit Girard Comment:https://github.com/w3c/csswg-drafts/issues/1305 Response:https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301600041 Changes:https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1 Closed: Accepted Resolved: Editorial Verified:https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301938166
Issue 3.# Summary: Specify how scroll-padding expands out From: Peter Linss Comment:https://github.com/w3c/csswg-drafts/issues/1050 Response:https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-301591832 Comment:https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-302840914 Response:https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-309578167 Changes:https://github.com/w3c/csswg-drafts/commit/38caa2ee20ca9833a1ad401b03c96debcac0cc21 Comment:https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-309591432 Closed: Accepted Resolved: Editorial Verified:https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-311517366
Issue 4.# Summary: Should negative scroll-padding be allowed From: fantasai Comment:https://github.com/w3c/csswg-drafts/issues/1084 Response:https://github.com/w3c/csswg-drafts/issues/1084#issuecomment-302153089 Changes:https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d Closed: Accepted Resolved: CSSWG Telecon 2017-05-17 Verified: Reporter is editor
Issue 5.# Summary: Clarify how visibility requirement makes snap x/y snap positions interdependent From: Majid Valipour Comment:https://github.com/w3c/csswg-drafts/issues/950 Response:https://github.com/w3c/csswg-drafts/issues/950#issuecomment-301597661 Changes:https://hg.csswg.org/drafts/diff/ae445d9c2266/css-scroll-snap/Overview.bs Closed: Accepted Resolved: Editorial
Issue 6.# Summary: scroll-snap-stop definition not quite right From: Majid Valipour Comment:https://github.com/w3c/csswg-drafts/issues/1552 Response:https://github.com/w3c/csswg-drafts/issues/1552#issuecomment-315480315 Changes:https://github.com/w3c/csswg-drafts/commit/09eac571148d01e1089a2b35c6293de0a3d605aa Closed: Accepted Resolved: Telecon 2017-07-19
Issue 7.# Summary: scroll-snap-stop definition implies applying to scroll container instead of snap position From: fantasai Changes:https://github.com/w3c/csswg-drafts/commit/256fa4d967add46f0c8b09987ed0b7970526473d Closed: Accepted Resolved: Editorial Verified: reporter is editor
Issue 8.# Summary: Add pageup/pagedown to From: Tab Atkins Comment:https://github.com/w3c/csswg-drafts/issues/1605 Changes:https://github.com/w3c/csswg-drafts/commit/098d2032876fdcd3cf2078bf0393e207b3e4b220 Closed: Accepted Resolved: Telecon 2017-07-19