RESOLVED FIXED64953
Fix SVG Font resources link in W3C SVG 1.1SE tests
https://bugs.webkit.org/show_bug.cgi?id=64953
Summary Fix SVG Font resources link in W3C SVG 1.1SE tests
Rob Buis
Reported 2011-07-21 08:56:40 PDT
Because the resources link to the SVG Font in these tests are wrong, an error is reported in the status bar of Safari. Fixing this does involve updating all results.
Attachments
Patch (897.26 KB, patch)
2011-07-21 10:07 PDT, Rob Buis
krit: review+
Rob Buis
Comment 1 2011-07-21 10:07:30 PDT
Dirk Schulze
Comment 2 2011-07-21 10:57:13 PDT
Comment on attachment 101601 [details] Patch Can you check if pixel possible platform specific pixel results can get removed before landing? I let the flag as r=? for now. You get r+ once chromium bot finished testing.
Dirk Schulze
Comment 3 2011-07-21 10:57:57 PDT
Comment on attachment 101601 [details] Patch Can you check if pixel possible platform specific pixel results can get removed before landing? I let the flag as r=? for now. You get r+ once chromium bot finished testing.
Rob Buis
Comment 4 2011-07-21 11:22:20 PDT
Hi Dirk, (In reply to comment #3) > (From update of attachment 101601 [details]) > Can you check if pixel possible platform specific pixel results can get removed before landing? I let the flag as r=? for now. You get r+ once chromium bot finished testing. Do you mean, now that we use SVG Fonts, we can move the results out of platform/ into W3C-SVG-11-SE? Cheers, Rob.
Dirk Schulze
Comment 5 2011-07-21 11:25:28 PDT
(In reply to comment #4) > Hi Dirk, > > (In reply to comment #3) > > (From update of attachment 101601 [details] [details]) > > Can you check if pixel possible platform specific pixel results can get removed before landing? I let the flag as r=? for now. You get r+ once chromium bot finished testing. > > Do you mean, now that we use SVG Fonts, we can move the results out of platform/ into W3C-SVG-11-SE? > Cheers, > > Rob. Would be great if it works. But might be a good reason for another bug :)
Rob Buis
Comment 6 2011-07-22 12:46:23 PDT
This got landed in r91493, closing.
Note You need to log in before you can comment on or make changes to this bug.