Closed
Bug 1157716
Opened 8 years ago
Closed 8 years ago
Mark unaccelerated antialiasing reftest failures on APZ as fuzzy
Categories
(Core :: Panning and Zooming, defect)
Core
Panning and Zooming
Tracking
()
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: dvander, Assigned: dvander)
References
Details
Attachments
(1 file)
33.08 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
No description provided.
![]() |
Assignee | |
Comment 1•8 years ago
|
||
Attachment #8596589 -
Flags: review?(mstange)
![]() |
Assignee | |
Comment 2•8 years ago
|
||
I based this off two try runs: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a2f5d44cf8df https://treeherder.mozilla.org/#/jobs?repo=try&revision=46e02e352b88 Doing a third now, so there might be a follow-up.
Comment 3•8 years ago
|
||
Might be worth seeing if these failures are cross-platform or not also.
Blocks: apz-desktop
![]() |
Assignee | |
Updated•8 years ago
|
Blocks: apz-windows
Comment 4•8 years ago
|
||
Comment on attachment 8596589 [details] [diff] [review] fix Please add an explanation in the commit message, something like this: With APZ we always layerize the first scrollable element of the page, if the page itself is not scrollable. These additional layers can cause fuzzy reftest failures in two ways: By differences in blending, or by disabling sub-pixel text anti-aliasing. The latter is only a problem with unaccelerated drawing, because we don't support component alpha layers with BasicLayers. (We also don't support them with BasicCompositor, but "Reftest unaccelerated" tests BasicLayers and not BasicCompositor.)
Attachment #8596589 -
Flags: review?(mstange) → review+
Comment 6•8 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9e6906a839ea
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox40:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
Comment 8•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/447ab3513385
You need to log in
before you can comment on or make changes to this bug.
Description
•