# CSS Scroll Snapping Level 1 Disposition of Comments for -2015-12 Draft

Dated Draft: https://drafts.csswg.org/css-scroll-snap/

Editor's Draft: http://drafts.csswg.org/css-scroll-snap/

The following color coding convention is used for comments:

- Accepted or Rejected and positive response
- Rejected and no response
- Rejected and negative response
- Deferred
- Out-of-Scope or Invalid and not verified

Open issues are marked like this

An issue can be closed as `Accepted`, `OutOfScope`, `Invalid`, `Rejected`, or `Retracted`. `Verified` indicates commentor's acceptance of the response.

    Issue 1. #
    Summary:  Rename 'proximity' and 'mandatory'
    From:     Sebastian Zartner
    Comment:  https://lists.w3.org/Archives/Public/www-style/2015Dec/0177.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016May/0006.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Sep/0099.html
    Closed:   Rejected
    Verified:
    Resolved: TPAC 2016

    Issue 2. #
    Summary:  Add property to define proximity capture distance
    From:     Sebastian Zartner
    Comment:  https://lists.w3.org/Archives/Public/www-style/2015Dec/0178.html
    Response: https://lists.w3.org/Archives/Public/www-style/2015Dec/0182.html
    Closed:   Deferred
    Verified: https://lists.w3.org/Archives/Public/www-style/2015Dec/0190.html
    Resolved: Editor's discretion

    Issue 3. #
    Summary:  Split 'scroll-snap-type' into longhands
    From:     fantasai
    Comment:  https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2015Dec/0108.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Apr/0101.html
    Response:
    Closed:   Deferred
    Verified: Reporter is editor
    Resolved: Editor discretion due to apathy of the WG & lack of names

    Issue 4. #
    Summary:  Should tracking an element snap position be required?
    From:     Matt Rakow
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0080.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0096.html
    Closed:   Accepted
    Verified: Reporter is editor
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Jan/0145.html

    Issue 5. #
    Summary:  Remove or maintain point-snapping
    From:     Matt Rakow
    Comment:  https://lists.w3.org/Archives/Public/www-style/2015Dec/0177.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0096.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0102.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0103.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0105.html
    Closed:   Deferred
    Verified: Reporter is editor
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Mar/0353.html

    Issue 6. #
    Summary:  Viewport snap target area terminology
    From:     Matt Rakow
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0080.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0096.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0096.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016May/0000.html
    Closed:   Accepted
    Verified: Reporter is editor
    Resolved: Editorial

    Issue 7. #
    Summary:  Logical alignment axis mismatches physical padding
    From:     Matt Rakow
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0090.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0133.html
    Closed:   Rejected
    Verified: https://lists.w3.org/Archives/Public/www-style/2016Jun/0020.html
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Jun/0020.html

    Issue 8. #
    Summary:  Remove or maintain 'edges' value?
    From:     Matt Rakow
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0090.html
    Response: ?
    Closed:   Deferred
    Verified: Reporter is editor
    Resolved: Editors' discretion

    Issue 9. #
    Summary:  Rename scroll-snap-area to scroll-snap-margin
    From:     fantasai  and Tab Atkins
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0095.html
    Closed:   Accepted
    Verified: Reporter is editor
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Jan/0145.html

    Issue 10. #
    Summary:  Need ability to skip content
    From:     François Remy
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0142.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0146.html
    Closed:   Invalid (already solved)
    Verified: https://lists.w3.org/Archives/Public/www-style/2016Jan/0164.html

    Issue 11. #
    Summary:  Imprecise wording wrt out-of-range snap positions
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0191.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0091.html
    Closed:   Accepted
    Resolved: Editorial

    Issue 12
    Summary:  Resnapping requirements wording
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0109.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0111.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0091.html
    Closed:   Accepted
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Jan/0145.html

    Issue 13. #
    Summary:  Clarify behavior of scroll-snap-align on scroll container
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0192.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0212.html
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0227.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0095.html
    Closed:   Accepted
    Resolved: Editorial

    Issue 14. #
    Summary:  Indirect scrolling
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0296.html #1
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0089.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0094.html
    Closed:   Accepted
    Resolved: Editorial

    Issue 15. #
    Summary:  Hostile mandatory snapping conflicting with target
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0296.html #2
    Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0089.html
    Closed:   Rejected
    Verified: https://log.csswg.org/irc.w3.org/css/2016-09-26/#e728994
    Resolved: Editors' discretion

    Issue 16. #
    Summary:  Application to pseudo-elements
    From:     Florian Rivoal
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Jan/0193.html
    Response: https://lists.w3.org/Archives/Public/www-style/2016Jan/0210.html
    Comment:  https://github.com/w3c/csswg-drafts/issues/488
    Response: https://github.com/w3c/csswg-drafts/issues/488#issuecomment-248139510
    Closed:   Rejected
    Verified: https://github.com/w3c/csswg-drafts/issues/488#issuecomment-248239965
    Resolved: https://lists.w3.org/Archives/Public/www-style/2016Mar/0353.html

    Issue 17. #
    Summary:  Extend scroll-snap-padding to handle related use cases
    From:     fantasai
    Comment:  https://lists.w3.org/Archives/Public/www-style/2016Feb/0081.html
    Response:
    From:     Florian Rivoal
    Comment:  https://github.com/w3c/csswg-drafts/issues/395
    Response: https://github.com/w3c/csswg-drafts/issues/395#issuecomment-249653721
    Closed:   Accepted
    Resolved: TPAC 2016

    Issue 18. #
    Summary:  Reflow should result in maintaining snap position
    From:     Scott Jehl
    Comment:  https://github.com/w3c/csswg-drafts/issues/155
    Response: https://github.com/w3c/csswg-drafts/issues/155#issuecomment-222843049
    Closed:   Invalid

    Issue 19. #
    Summary:  Add events for snapping
    From:     Scott Jehl
    Comment:  https://github.com/w3c/csswg-drafts/issues/156
    Response: https://github.com/w3c/csswg-drafts/issues/156#issuecomment-249655183
    Closed:   Deferred