Closed
Bug 1488403
Opened 7 years ago
Closed 7 years ago
Make sticky legend reftest not rely on groove border antialising.
Categories
(Core :: Graphics: WebRender, enhancement, P1)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(1 file)
This is failing with my patch to fix groove borders because of a slight antialising difference:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=0e3afa2058fd3f1ed19af3a2fd9eec0e9e817704
I'll explain in the commit message why I think we shouldn't worry about it.
| Assignee | ||
Comment 1•7 years ago
|
||
This reftest fails with my changes from
https://github.com/servo/webrender/pull/3010. I tried to debug locally but it
passes here.
The reason it fails is because WebRender does distance AA between the segments
of a ridge / groove border, and there's a subpixel difference so we get the AA
slightly different in the test.
Gecko on the other hand represents these borders as different composed solid
segments, so it can't have this problem, since it doesn't do AA across the
segments.
We may want to change that, but it's not clear to me it's wanted, since rounded
corners for these look much better on WR, for example.
Rather than fuzzing the test or something like that, make the test not rely on
that, given it's testing the position of the legend.
Comment 2•7 years ago
|
||
Comment on attachment 9006235 [details]
Make sticky legend reftest not depend on groove border antialising.
Nicolas Silva [:nical] has approved the revision.
Attachment #9006235 -
Flags: review+
Pushed by emilio@crisal.io:
https://hg.mozilla.org/integration/autoland/rev/e4f3b85bc61b
Make sticky legend reftest not depend on groove border antialising. r=nical
Updated•7 years ago
|
Blocks: stage-wr-trains
Priority: -- → P1
Comment 4•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•