Issue metadata
Sign in to add a comment
|
An <svg> with "position: absolute" inside a <foreignObject> is not positioned correctly
Reported by
yhe...@gmail.com,
Jan 22 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Render this scenario as in the attached file 2. Set the zoom level to any value other than 100% 3. What is the expected behavior? The yellow rectangle should cover the green parent <div>. What went wrong? When the zoom level is other than 100%, the yellow rectangle is transposed to the right and thus some of the parent <div> is revealed to the left. Did this work before? Yes 58 Does this work in other browsers? Yes Chrome version: 63.0.3239.132 Channel: stable OS Version: 4.4.0-104 Flash Version: It works on other browsers and worked on older versions of Chrome (up to 58).
,
Jan 22 2018
Yes, it is the same underlying problem with all our foreign object layer positioning issues.
,
Jan 22 2018
Thank you for the information and sorry for the duplicate bug report.
,
Jan 22 2018
Hello schenney@chromium.org, I'm replying here to not cause lots of notifications for all the people that are watching 771852. According to this comment: https://bugs.chromium.org/p/chromium/issues/detail?id=771852#c24 especially the line > Cr-Commit-Position: refs/heads/master@{#529919} and this information https://www.chromium.org/blink/when-will-a-fix-ship-in-chrome-stable-or-canary https://www.chromium.org/developers/calendar I found that the current carnary version should contain the fix for this issue, right? (Since their is no Carnary for unix) I downloaded the latest version form here: http://download-chromium.appspot.com/ (the page currently says it is "Build Revision: 530933" which says it is version "Version 66.0.3329.0 (Developer Build) (64-bit)" And the bugfix should also be contained in that version, right? I ran the example attached to this ticket in that version and it is still broken (see attached screenshot at zoom level 125%. Can you help us to understand the situation to be able to communicate the approximate arrival of a fix in the Chrome browser? Thx
,
Jan 22 2018
We're still burning down the bug list for the changes that will fix this, so it should not be fixed in Canary. The comment by chrishtr@ over on 771852 describes the current state of affairs.
,
Jan 22 2018
Thx for the clarifications! I now understood that the comment 24 marks a related merge to master/trunk, but not a not the comlete fix and 771852 is still the ticket to follow to get notified about the status. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yhe...@gmail.com
, Jan 22 2018