- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2019 17:27:13 +0000
- To: public-css-archive@w3.org
@tunelinks your concerns are already handled in the spec with this language... > If the content or layout of the document changes (e.g. content is added, moved, deleted, resized) such that the content of a snapport changes, the UA must re-evaluate the resulting scroll position, and re-snap if required. If the scroll container was snapped before the content change and that same snap position still exists (e.g. its associated element was not deleted), the scroll container must be re-snapped to that same snap position after the content change. > https://drafts.csswg.org/css-scroll-snap/#snap-strictness Though implementors have yet to implement this logic. Chime in on filings like these to encourage implementation. - https://bugs.chromium.org/p/chromium/issues/detail?id=866127 - https://www.chromestatus.com/feature/5865619656278016 Also, your concern isn't exactly related to the original issue above. -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/156#issuecomment-492332223 using your GitHub account
Received on Tuesday, 14 May 2019 17:27:14 UTC