RESOLVED INVALID 86062
[Gtk] Two SVG reftests failing after r116498
https://bugs.webkit.org/show_bug.cgi?id=86062
Summary [Gtk] Two SVG reftests failing after r116498
Zan Dobersek
Reported 2012-05-10 00:06:28 PDT
The following SVG reftests are consistently failing with image mismatches: svg/text/add-tspan-position-bug.html svg/text/modify-tspan-position-bug.html They were both added in r116498.
Attachments
svg/text/add-tspan-position-bug.html image diff (4.71 KB, image/png)
2012-05-10 00:26 PDT, Zan Dobersek
no flags
svg/text/modify-tspan-position-bug.html image diff (4.71 KB, image/png)
2012-05-10 00:27 PDT, Zan Dobersek
no flags
Zan Dobersek
Comment 1 2012-05-10 00:26:35 PDT
Created attachment 141096 [details] svg/text/add-tspan-position-bug.html image diff
Zan Dobersek
Comment 2 2012-05-10 00:27:14 PDT
Created attachment 141098 [details] svg/text/modify-tspan-position-bug.html image diff
Alexey Proskuryakov
Comment 3 2012-05-10 11:53:36 PDT
Please feel free to always CC author and reviewer of an offending change.
Tim Horton
Comment 4 2012-05-10 12:10:09 PDT
Can you post screenshots of what loading the two tests manually looks like, please?
Zan Dobersek
Comment 5 2012-05-11 00:09:13 PDT
(In reply to comment #4) > Can you post screenshots of what loading the two tests manually looks like, please? When loading manually the text is displayed and laid out as expected in both tests. Delaying the layoutTestController.notifyDone() call a bit (tested 50 and 100 ms) for a redraw to happen seems to help, the tests pass then.
Zan Dobersek
Comment 6 2012-05-12 00:25:21 PDT
The tests were rolled out in r116801, marking this bug invalid. Should be reopened when/if the changes are again committed into the tree. 1: http://trac.webkit.org/changeset/116801
Zan Dobersek
Comment 7 2012-05-12 08:44:28 PDT
Just as an additional note, the problem is fixable by doing another repaint before dumping pixel results in DRT. This is obviously not a problem introduced in r116498 but will rather be handled in bug #86284.
Note You need to log in before you can comment on or make changes to this bug.