Closed Bug 958005 Opened 12 years ago Closed 11 years ago

CSSKeyframesRule.findRule is treating the argument as a keyframe selector, not a number

Categories

(Core :: CSS Parsing and Computation, defect)

26 Branch
x86_64
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: colouredchalkmelky, Unassigned)

References

Details

(Keywords: css3)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 Steps to reproduce: Coding css3 animation via JavaScript ---> filling keyframesRule exactly. I try to find rule .. I'm passing DOMString as first argument. Example : CSSKeyframesRule.findRule("0") If I pass it with "%" postfix, it returns correct value Example : CSSKeyframesRule.findRule("0%") But "0%" is incorrect DOMString value. Actual results: CSSKeyframesRule.findRule returns null always with correct environment and correct arguments passed. Expected results: It should return correct CSSKeyframeRule (for DOMString like for postprefixed version).
Component: Untriaged → CSS Parsing and Computation
Keywords: css3
Product: Firefox → Core
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [CSS3 ANIMATIONS] wrong adherence to the specification → CSSKeyframesRule.findRule is treating the argument as a keyframe selector, not a number
David, how stable is this part of the spec?
Flags: needinfo?(dbaron)
I really don't know. How well does it agree with implementations, and if there's disagreement, is the movement in one direction or another?
Flags: needinfo?(dbaron)
Chrome has the same behavior. IE - nope. Please take a look at that, may be it can help: http://lists.w3.org/Archives/Public/www-style/2013Feb/0587.html Working Draft -> 19 February 2013 That mailing list -> 22 Feb 2013 So, may be they will update spec soon.
If browsers agree, it makes more sense to change the spec than change all the browsers.
(Also, I think the argument being a keyframe selector makes a lot more sense than being a number.)
Yeah, agreed. I guess we keep this open until the spec is fixed...
Agreed too. IE throws an exception for wrong arg. Still, a web-programmer can use simple workaround to make it work.
http://dev.w3.org/csswg/css-animations/#interface-csskeyframesrule-findrule now says the argument is supposed to be a percentage value, which means our behavior is now correct.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: