Bug 53082

Summary: SVG: "margin" style not properly applied to xhtml foreignObjects
Product: WebKit Reporter: Berend-Jan Wever <skylined>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ahmad.saleem792, eric, sabouhallawa, simon.fraser, zalan, zimmermann
Priority: P1    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows Vista   
Attachments:
Description Flags
SVG version - displays X too high
none
XHTML version - displays X located correctly none

Berend-Jan Wever
Reported 2011-01-25 06:32:32 PST
Created attachment 80057 [details] SVG version - displays X too high Chromium bug: http://code.google.com/p/chromium/issues/detail?id=70758 Repro = compare visually: <?xml version="1.0" standalone="yes"?> <html xmlns="http://www.w3.org/1999/xhtml"> <body style="margin:50px"> X </body> </html> and <?xml version="1.0" standalone="yes"?> <svg xmlns="http://www.w3.org/2000/svg"> <foreignObject x="0" y="0" width="100%" height="100%"> <body xmlns="http://www.w3.org/1999/xhtml" style="margin:50px"> X </body> </foreignObject> </svg> The later (SVG) version does not apply the margin on the TOP, so the X is not displayed in the correct location.
Attachments
SVG version - displays X too high (257 bytes, image/svg+xml)
2011-01-25 06:32 PST, Berend-Jan Wever
no flags
XHTML version - displays X located correctly (140 bytes, application/xhtml+xml)
2011-01-25 06:33 PST, Berend-Jan Wever
no flags
Berend-Jan Wever
Comment 1 2011-01-25 06:33:07 PST
Created attachment 80058 [details] XHTML version - displays X located correctly
Ahmad Saleem
Comment 2 2022-05-30 05:32:07 PDT
I am still able to reproduce the following issue from the attached test case "display X too high" on Safari 15.5 (macOS 12.4). It renders fine on Chrome Canary 104 and Firefox Nightly 102. Chrome fixed this issue in 2016 in this bug - https://bugs.chromium.org/p/chromium/issues/detail?id=226805 Thanks!
Ahmad Saleem
Comment 3 2022-10-12 06:57:21 PDT
Ahmad Saleem
Comment 4 2022-12-02 16:06:25 PST
*** This bug has been marked as a duplicate of bug 245908 ***
Note You need to log in before you can comment on or make changes to this bug.