Closed Bug 1474536 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 11880 - Don't assume opacity computed values are exactly the same as specified on keyframe input

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox63 fixed)

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 11880 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/11880
Details from upstream follow.

 wrote:
>  Don't assume opacity computed values are exactly the same as specified on keyframe input
>  
>  The CSS Color Module Level 3 specification defines the [opacity](https://drafts.csswg.org/css-color-3/#opacity) property as taking <number> values. Meanwhile, the CSS Values and Units Module Level 3 specification [discusses the precision of numeric data types](https://drafts.csswg.org/css-values-3/#numeric-types) like so:
>  
>  > CSS theoretically supports infinite precision and infinite ranges for all value types; however in reality implementations have finite capacity. UAs should support reasonably useful ranges and precisions.
>  
>  This test fails in WebKit because it requires the provided value to be round-tripped through the computed style even though they cannot all be represented as precisely as the test entails. We update the test to compare values with a small alpha.
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9a66e4a2963b
[wpt PR 11880] - Don't assume opacity computed values are exactly the same as specified on keyframe input, a=testonly
https://hg.mozilla.org/mozilla-central/rev/9a66e4a2963b
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.