NEW 190000
[GTK] svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg fails
https://bugs.webkit.org/show_bug.cgi?id=190000
Summary [GTK] svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg fails
Alicia Boya García
Reported 2018-09-26 09:28:47 PDT
This new test is failing on GTK: svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/svg/W3C-SVG-1.1-SE/svgdom-over-01-f-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/svg/W3C-SVG-1.1-SE/svgdom-over-01-f-actual.txt @@ -88,11 +88,11 @@ RenderSVGText {text} at (10,-1) size 360x10 contains 1 chunk(s) RenderSVGInlineText {#text} at (0,0) size 360x9 chunk 1 text run 1 at (10.00,7.00) startOffset 0 endOffset 70 width 360.00: "g.gradientUnits.baseVal == 2 (SVG_UNIT_TYPE_OBJECTBOUNDINGBOX): PASSED" - RenderSVGContainer {g} at (10,189) size 157x10 [transform={m=((1.00,0.00)(0.00,1.00)) t=(10.00,190.00)}] + RenderSVGContainer {g} at (10,189) size 145x10 [transform={m=((1.00,0.00)(0.00,1.00)) t=(10.00,190.00)}] RenderSVGRect {rect} at (10,191) size 5x5 [fill={[type=SOLID] [color=#00FF00]}] [x=0.00] [y=1.00] [width=5.00] [height=5.00] - RenderSVGText {text} at (10,-1) size 147x10 contains 1 chunk(s) - RenderSVGInlineText {#text} at (0,0) size 147x9 - chunk 1 text run 1 at (10.00,7.00) startOffset 0 endOffset 33 width 147.00: "f.filterResX.baseVal == 0: PASSED" + RenderSVGText {text} at (10,-1) size 135x10 contains 1 chunk(s) + RenderSVGInlineText {#text} at (0,0) size 135x9 + chunk 1 text run 1 at (10.00,7.00) startOffset 0 endOffset 29 width 135.00: "c.orderX.baseVal == 0: PASSED" RenderSVGContainer {g} at (10,199) size 192x10 [transform={m=((1.00,0.00)(0.00,1.00)) t=(10.00,200.00)}] RenderSVGRect {rect} at (10,201) size 5x5 [fill={[type=SOLID] [color=#00FF00]}] [x=0.00] [y=1.00] [width=5.00] [height=5.00] RenderSVGText {text} at (10,-1) size 182x10 contains 1 chunk(s)
Attachments
Simon Fraser (smfr)
Comment 1 2018-09-28 14:35:30 PDT
filterRes was removed, so this just needs a new baseline.
Note You need to log in before you can comment on or make changes to this bug.