- From: Simon Fraser via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2020 01:39:29 +0000
- To: public-css-archive@w3.org
You'd pixel-snap both for painted scrolled content, and for composited scrolled content, right? Having the scroll offsets be unsnapped might lead to the usual floating point comparison issues, especially with scroll snapping, or JS trying to determine whether the scroll offset is the same as some previous offset. This could also be a problem in implementations. Also note that on macOS and iOS at least, the native scrollers always use pixel-snapped values, meaning that on these platforms we'd continue to snap the actual scroller offsets. I think I'd prefer that the actual scroll offsets are snapped. -- GitHub Notification of comment by smfr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4717#issuecomment-580543161 using your GitHub account
Received on Friday, 31 January 2020 01:39:30 UTC