Closed Bug 1771243 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 34212 - Drop animation-* properties in @keyframes at parse time

Categories

(Core :: CSS Transitions and Animations, task, P4)

Product:
Core
Component:
CSS Transitions and Animations
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
103 Branch
Tracking Flags:
Tracking Status
firefox103 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

Drop animation-* properties in @keyframes at parse time

... since they (except animation-timing-function) aren't allowed there:

https://drafts.csswg.org/css-animations/#typedef-keyframe-block

Fixed: 1329311
Change-Id: If6799076f6447ddfe21c10d4bf00b5519536e9ae
Reviewed-on: https://chromium-review.googlesource.com/3669740
WPT-Export-Revision: 983edc153cba8aafea7e5d4cdb0e4776914403e4

Component: web-platform-tests → CSS Transitions and Animations
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f2b16d688d13 [wpt PR 34212] - Drop animation-* properties in @keyframes at parse time, a=testonly https://hg.mozilla.org/integration/autoland/rev/44de2c9147a9 [wpt PR 34212] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/f2b16d688d13
https://hg.mozilla.org/mozilla-central/rev/44de2c9147a9

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox103: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in before you can comment on or make changes to this bug.