Bug 100139
| Summary: | [Chromium] Align layout runner flags Android uses with the product that's being shipped | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Peter Beverloo <peter> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | skyostil |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 100263 | ||
| Bug Blocks: | |||
Peter Beverloo
There are some differences right now between the flags used in Chromium for Android and what DumpRenderTree gets passed for running layout tests. For the most accurate results, these should be synchronized as much as possible.
When we switch to using content_shell as the test runner, this should also become much easier to keep in sync..
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Sami Kyöstilä
I was planning to add two flags: --force-composited-mode and --enable-accelerated-fixed-position (new flag).
We'd also need --enable-threaded-compositing but current it crashes the test runner.
Peter Beverloo
Resolving as WontFix given that Chromium moved to Blink.