94353 2012-08-17 09:43:33 -0700 [Chromium] Turn on ENABLE_OVERFLOW_SCROLLING 2013-04-09 17:06:54 -0700 1 1 1 Unclassified WebKit Platform 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 91117 1 skyostil skyostil dominicc dpranke oldest_to_newest 698422 0 skyostil 2012-08-17 09:43:33 -0700 ENABLE_OVERFLOW_SCROLLING is currently disabled in features.gypi (except for Android). We should turn it on by default if possible. 705029 1 dominicc 2012-08-27 01:11:26 -0700 I rebaselined some tests with expectations pointing to this bug in r126734, I would appreciate it if you could sanity check me on the rebaselines. 707439 2 skyostil 2012-08-29 07:46:01 -0700 This is a bit weird since the original baselines had the expected result when OVERFLOW_SCROLLING is on, but the new ones are generated with OVERFLOW_SCROLLING disabled. The former were meant as a golden sample against which composited scrolling could be verified. I guess having baselines from non-standard build configurations isn't really sustainable, so let's keep the new ones for now and revisit once we can flip the switch for OVERFLOW_SCROLLING. 723147 3 dpranke 2012-09-18 17:33:45 -0700 Looks like compositing/overflow/overflow-auto-with-touch-toggle.html is no longer failing either, for some reason. 723148 4 dpranke 2012-09-18 17:35:38 -0700 http://trac.webkit.org/changeset/128951 872478 5 schenney 2013-04-09 17:06:54 -0700 Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.