Summary: | Fix CSSKeyframesRule & CSSKeyframeRule types in the IDL | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | LEPESME Jean-Baptiste <lepesme.jb> | ||||||
Component: | CSS | Assignee: | Chris Marrin <cmarrin> | ||||||
Status: | RESOLVED CONFIGURATION CHANGED | ||||||||
Severity: | Minor | CC: | ahmad.saleem792, ap, bfulgham, dino, rniwa, simon.fraser, zalan | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 7 | ||||||||
Attachments: |
|
Description
LEPESME Jean-Baptiste
2009-08-21 10:36:47 PDT
Created attachment 38428 [details]
change VARIABLES_RULES to 9, and set the correct value to KEYFRAMES_RULE and KEYFRAME_RULE
I made some research and I figured out that the css-variables features of webkit is non "standard" and not intended to be a part of CSS3. It seems to be based on http://disruptive-innovations.com/zoo/cssvariables/ wich use RuleType number 7. As css-animations should be in CSS3, i think that webkit had to change VARIABLES_RULES to another value to respect http://www.w3.org/TR/css3-animations/ . Bye, Jiboo. We should really be using values outside the reserved range for features that are not yet in CR. In attached test case, I get across all browsers (Safari 15.6, Chrome Canary 106 and Firefox Nightly 104) below: [object CSSKeyframesRule].type = 7 [object CSSKeyframeRule].type = 8 It is expected result as of Comment 0 and I think it was fixed along the way and now this bug can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks! |