100x CSS translation of small position results in inaccurate painting
Reported by
leonger...@gmail.com,
Jan 1 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9901.77.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.97 Safari/537.36 Platform: 9901.77.0 (Official Build) stable-channel caroline Steps to reproduce the problem: 1. Use a CSS 3d transform to move an element 2. Inspect the element using the developer tools What is the expected behavior? The element is painted per the CSS specification, and in the position indicated by the developer tools. What went wrong? The element is painted in another position. The element inspector shows the position that would be expected according to the spec, but the actual paint is elsewhere. Attached screenshot shows an inspection of the element. The line on the left shows where developer tools thinks the element is. This is the correct location. The line on the right is where the element is actually painted. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.97 Channel: stable OS Version: 9901.77.0 Flash Version: Attached test case produces expected results in firefox 57.
,
Jan 2 2018
We might be able to do better with rounding, but re-arranging the computation to reduce rounding artifacts is likely to be very hard. The underlying issue is probably snapping the div location to layout units then scaling afterwards.
,
Jan 2
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 14
Really should look into this, because it's still happening. |
||||
►
Sign in to add a comment |
||||
Comment 1 by leonger...@gmail.com
, Jan 1 2018