Closed Bug 1660626 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 25200 - Will-change: opacity should create a stacking context for inlines

Categories

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

task

Tracking

(firefox82 fixed)

RESOLVED FIXED
82 Branch
Tracking Status
firefox82 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Philip Rogers <pdr@chromium.org> wrote:

Will-change: opacity should create a stacking context for inlines

The spec [1] states that will-change: opacity should create a stacking
context for inlines in the same way that non-zero opacity does. This was
fixed by https://crrev.com/776581 ("Unify CSS grouping properties") but
we didn't have a testcase. This patch adds a WPT test of this behavior.

[1] https://drafts.csswg.org/css-will-change/#will-change

Bug: 1119651
Change-Id: I7abd4006b61039d9302f8ac9036848aeb37df476
Reviewed-on: https://chromium-review.googlesource.com/2370095
WPT-Export-Revision: 600dfb7f9d34d97c5d5177784366b0df80a478d8

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7103befab061
[wpt PR 25200] - Will-change: opacity should create a stacking context for inlines, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in before you can comment on or make changes to this bug.