Issue metadata
Sign in to add a comment
|
SVG foreign object should clip descendants. |
||||||||||||||||||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win7, OSX 10.9.5, etc...) What steps will reproduce the problem? (1) Visit http://jsbin.com/damonik/edit?html,output What is the expected result? Expect the green box to be 100x100. What happens instead? Instead, in chrome 56.0.2924.87 it is oddly drawn to the next tile boundary (resize the html view and see the size change) and in 58.0.3023.0 it is clipped to the svg box (200x200). Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Feb 28 2017
,
Mar 6 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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 6 2018
Still wrong. One to fix in the course of Slimming Paint, maybe, or adjusting adjusting the containing block model.
,
Mar 7 2018
In SPv175, if overflow:hidden is added to <foreignObject>, this example will draw as expected. @fs: seems we should add overflow:hidden to the UA stylesheet for foreignObject?
,
Mar 7 2018
We have that already [1], so something more must be broken. (The mixed case has been trouble before...) [1] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/css/svg.css?type=cs&l=48
,
Mar 7 2018
Weird. Adding overflow:hidden to the <foreignObject> fixes it.
,
Mar 7 2018
I hacked svg.css to lowercase foreignObject and it worked. Bug in CSS.
,
Mar 7 2018
Looks like the other rules that should apply to foreignObject also don't apply. Similarly with textPath so almost certainly something with the camelCase.
,
Mar 7 2018
It seems to work for an invented tag, and camelCase-ing existing elements like <div>. Seems to be something special about SVG parsing. Maybe SVG elements have a special parser?
,
Mar 7 2018
When inline in HTML <svg> will cause the HTML parser to switch to "foreign content mode" the HTML parser (tree builder) is then supposed to normalize the local name. I think that's the interesting bit parsing-wise. There are additional quirks wrt HTML casing and selectors.
,
Mar 7 2018
I broke off issue 819814 for the CSS issue. Dup-ing the rest into 771852. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by schenney@chromium.org
, Feb 27 2017Status: Available (was: Untriaged)