- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Mar 2019 06:00:38 +0000
- To: public-css-archive@w3.org
In particular, it sounds like, in Chromium, the pixels being snapped to are a function of what does or doesn't have a layer in the compositor... which means that this is exposing that, and thus likely causing some sites to depend, for correct behavior (not just for performance), on particular layerization. I think Gecko might pixel snap across rectilinear transforms (translate and scale only), whereas it sounds like Chromium doesn't. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3554#issuecomment-468553173 using your GitHub account
Received on Friday, 1 March 2019 06:00:39 UTC