WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
272440
[css-animations] CSS animation="none" property should stay as is
https://bugs.webkit.org/show_bug.cgi?id=272440
Summary
[css-animations] CSS animation="none" property should stay as is
Karl Dubost
Reported
2024-04-09 22:42:20 PDT
Enter in STP 191 data:text/html,<div%20style="animation:none"></div> In the Web Inspector console, type document.querySelector('div').style.getPropertyValue('animation') It returns 0s instead of none. This fails the test
http://wpt.live/css/css-animations/parsing/animation-valid.html
http://wpt.fyi/css/css-animations/parsing/animation-valid.html
Firefox and Chrome return the correct value.
Attachments
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2024-04-09 22:45:10 PDT
<
rdar://problem/126186241
>
Antoine Quint
Comment 2
2024-04-10 02:36:43 PDT
This test was added in
https://github.com/web-platform-tests/wpt/commit/ec49f0a0b605c79a343c9e6a12126502cee58638
and is related to the change in the CSS Animations spec to report `auto` instead of `0s` as the default animation-duration value. Compare and contrast:
https://drafts.csswg.org/css-animations-1/#animation-duration
https://drafts.csswg.org/css-animations-2/#animation-duration
This is part of the scroll-linked animations work.
Karl Dubost
Comment 3
2025-10-23 14:46:38 PDT
Everything is green on.
http://wpt.fyi/results/css/css-animations/parsing/animation-valid.html
BUT data:text/html,<div%20style="animation:none"></div> document.querySelector('div').style.getPropertyValue('animation') NOW returns on STP 230: "auto" Firefox: "none" Chrome: "auto ease 0s 1 normal none running none"
Karl Dubost
Comment 4
2025-10-23 14:48:05 PDT
Probably the better test is now
http://wpt.fyi/results/css/css-animations/parsing/animation-computed.html
Antoine Quint
Comment 5
2025-10-24 00:05:48 PDT
Both the WPT tests listed are green on Safari (and Firefox). Should we close this?
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug