Explicitly set `layout.scroll.disable-pixel-alignment` to true at the top directory of web platform tests.
Categories
(Core :: Panning and Zooming, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
Bug 1953979 - remove expectations for animation related subtests because they're passing now. r=hiro
48 bytes,
text/x-phabricator-request
|
Details | Review |
With disabling pixel alignments there are a bunch of unexpected pass web platform tests. That's a good outcomes of disabling pixel alignments. But if we had to revert the pref change for some reasons, e.g. unexpected regressions or some such, we also need to revert web platform annotation changes too. To avoid it, we are going to set the pref layout.scroll.disable-pixel-alignment
at the top of web platform test directory so that the unexpected pass web platform tests keep passing regardless of the default pref value.
Assignee | ||
Comment 1•1 month ago
|
||
Updated•1 month ago
|
Assignee | ||
Comment 2•1 month ago
|
||
Updated•1 month ago
|
Backed out for causing wpt failures @overscroll-behavior-root.html.
Assignee | ||
Comment 5•1 month ago
|
||
Filed bug 1954403 to fix the failure. The failure message is;
overscroll-behavior in root works - promise_test: Unhandled rejection with value: "error: Action action_sequence failed: Expected \"y\" to be an Integer, got [object Number] 772.4000244140625\nstacktrace:\n\tRemoteError@chrome://remote/content/shared/RemoteError.sys.mjs:8:8\n\tWebDriverError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:199:5\n\tInvali
I can see this error locally on my Linux box with --setpref="layout.css.devPixelsPerPx=1.7" --headless
options.
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 10•1 month ago
|
||
bugherder |
Comment 11•1 month ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Description
•