Issue metadata
Sign in to add a comment
|
Translucent elements (via opacity) inside foreignobject are rendered at a wrong scale on HiDPI displays
Reported by
julien.s...@gmail.com,
Mar 20 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Example URL: http://codepen.io/gentooboontoo/pen/zZRqad Steps to reproduce the problem: Open http://codepen.io/gentooboontoo/pen/zZRqad on a (Linux ?) station with HiDPI display (a full HD laptop for instance) What is the expected behavior? Blocks (with or without opacity set) fill their parent SVG element. What went wrong? Translucent blocks are rendered at a wrong scale. Chromium does not seem to take into account the scaling factor for translucent elements on HiDPI displays. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.98 Channel: n/a OS Version: Flash Version: According to my own tests, it works flawlessly on Firefox with HiDPI display or Chrome on a Linux station with LoDPI display. I cannot test whether the problem also occurs on non-Linux HiDPI devices.
,
Mar 20 2017
,
Mar 20 2017
This has been fixed at some point. It reproduces on Windows HighDPI (any screen scale setting more than 100% on Win 10) Version 57.0.2987.88 beta (64-bit) but does not reproduce in Version 59.0.3033.1 canary SyzyASan.
,
Mar 20 2017
Need a bisect to see if there's something we can merge back.
,
Mar 20 2017
The problem is still present (same test case) on Linux with the latest Chromium build (59.0.3047.0).
,
Mar 20 2017
,
Mar 22 2017
,
Apr 7 2017
Able to reproduce issue on Win-10 high DPI machine using chrome reported version #57.0.2987.98 and latest canary #59.0.3064.0. Bisect Information: ===================== Good build: 54.0.2793.0 Revision(404564) Bad Build : 54.0.2795.0 Revision(405182) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/af2f49ba57ed217d06e69830f325c9ba7e7ce0bd..57b70dae30c2bc7d60e70efd8ebae83e01fe9119 Unable to find any possible suspect from the above change log. Could anyone from dev team please help us in assigning it to the right owner. Thanks...!!
,
Apr 7 2017
Out of that list, f449a7f4828a5610b1e21b8d2e378555fa59ca7b seems most likely to have an impact.
,
Apr 11 2017
So we're looking at some place where zoom is not applied but the old deviceScaleFactor was.
,
Apr 12 2017
Based on current discussion here, this does not appear to be threaded-rendering related. Please re-add label with reason if you disagree.
,
Apr 13 2018
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
,
Apr 13 2018
Fixed in Canary no doubt due to SPv175.
,
Apr 13 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Mar 20 2017