compositing/geometry/limit-layer-bounds-fixed-positioned.html gives different results in WebKit2
https://bugs.webkit.org/show_bug.cgi?id=81679
Summary compositing/geometry/limit-layer-bounds-fixed-positioned.html gives different...
mitz
Reported 2012-03-20 10:59:27 PDT
As of r111400, compositing/geometry/limit-layer-bounds-fixed-positioned.html is failing: <http://build.webkit.org/results/Lion%20Intel%20Debug%20(Tests)/r111389%20(4654)/compositing/geometry/limit-layer-bounds-fixed-positioned-pretty-diff.html> --- /Volumes/Data/slave/lion-intel-debug-tests/build/layout-test-results/compositing/geometry/limit-layer-bounds-fixed-positioned-expected.txt +++ /Volumes/Data/slave/lion-intel-debug-tests/build/layout-test-results/compositing/geometry/limit-layer-bounds-fixed-positioned-actual.txt @@ -15,7 +15,7 @@ (drawsContent 1) ) (GraphicsLayer - (position 0.00 113.00) + (position 0.00 13.00) (bounds 150.00 142.00) (drawsContent 1) ) I am going to commit this change to the expected results.
Attachments
Radar WebKit Bug Importer
Comment 1 2012-03-20 11:00:22 PDT
mitz
Comment 2 2012-03-20 11:03:15 PDT
Updated the expected results in <http://trac.webkit.org/r111412>.
mitz
Comment 3 2012-03-20 12:00:39 PDT
(In reply to comment #2) > Updated the expected results in <http://trac.webkit.org/r111412>. This just introduced a failure on Lion Intel Debug (WebKit2 Tests).
mitz
Comment 4 2012-03-20 12:10:11 PDT
I updated the title to say that the problem is that this tests gives different results in WebKit2.
mitz
Comment 5 2012-03-20 12:53:10 PDT
Added Mac WebKit2 expected results in <http://trac.webkit.org/r111427> (by copying the generic results as they were before r111412).
Note You need to log in before you can comment on or make changes to this bug.