[wpt-sync] Sync PR 50069 - Compute after-change style if necessary
Categories
(Core :: CSS Transitions and Animations, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox136 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 50069 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/50069
Details from upstream follow.
Rune Lillesveen <futhark@chromium.org> wrote:
Compute after-change style if necessary
The base style from StyleBaseData was used as the after-change style for
starting CSS transitions. That works as long as the base style does not
inherit animation effects from ancestors.Detect that we need to cascade after-change style separately by walking
the ancestors of the element we are handling transitions for, checking
if any ancestors are animating the property we consider a transition
for. If necessary, compute the after-change style as far up as
necessary.The after-change style is only cached for the element that's currently
being resolved.Bug: 40337057
Change-Id: I6bfcb02f8935605d4f286a16fe1dafe717499509
Reviewed-on: https://chromium-review.googlesource.com/6110431
WPT-Export-Revision: c021e03897d469d0334f2c6178f06aea279cd39d
Assignee | ||
Updated•1 month ago
|
Assignee | ||
Comment 1•1 month ago
|
||
Assignee | ||
Comment 2•1 month ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 2 subtests
Status Summary
Firefox
OK
: 1
PASS
: 2
Chrome
OK
: 1
FAIL
: 2
Safari
OK
: 1
FAIL
: 2
Links
Comment 4•1 month ago
|
||
bugherder |
Description
•