Bug 94353
| Summary: | [Chromium] Turn on ENABLE_OVERFLOW_SCROLLING | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sami Kyöstilä <skyostil> |
| Component: | Platform | Assignee: | Sami Kyöstilä <skyostil> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | dominicc, dpranke |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 91117 | ||
| Bug Blocks: | |||
Sami Kyöstilä
ENABLE_OVERFLOW_SCROLLING is currently disabled in features.gypi (except for Android). We should turn it on by default if possible.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dominic Cooney
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.
Sami Kyöstilä
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.
Dirk Pranke
Looks like compositing/overflow/overflow-auto-with-touch-toggle.html is no longer failing either, for some reason.
Dirk Pranke
http://trac.webkit.org/changeset/128951
Stephen Chenney
Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.