[Webkit-unassigned] [Bug 96382] Android's mock scrollbars shows up as a difference in layout test results

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=96382


Peter Beverloo <peter at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abarth at webkit.org,
                   |                            |dpranke at chromium.org,
                   |                            |tony at chromium.org,
                   |                            |wangxianzhu at chromium.org




--- Comment #1 from Peter Beverloo <peter at chromium.org>  2012-09-12 06:03:41 PST ---
I'm not sure we can address this without needing new Android baselines for every test that has a scrollbar. Windows, Mac and Linux do the same (see links below).

Our scrollbars are painted using the compositor, which we force to be on in the shipping version of the product itself. I think the best way forward would be to have these show up on the pixel results (i.e. what the product itself uses), and then submit a few massive commits with baselines.

Ideas / confirmation before I do this would be most welcome!


Another example output:
http://build.webkit.org/results/Chromium%20Android%20Release%20(Tests)/r128190%20(72)/css2.1/t1202-counters-09-b-diffs.html

Mac example:
http://build.webkit.org/results/Chromium%20Mac%20Release%20%28Tests%29/r128297%20%2823853%29/fast/block/float/028-diffs.html

Windows using mock scrollbars:
http://build.webkit.org/results/Chromium%20Win%20Release%20%28Tests%29/r128290%20%2829919%29/fast/block/float/028-diffs.html

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.