[Bug 25035] New: The side-effects of programmatically duplicating a rule key are undefined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25035

            Bug ID: 25035
           Summary: The side-effects of programmatically duplicating a
                    rule key are undefined
           Product: CSS
           Version: unspecified
          Hardware: All
               URL: http://lists.w3.org/Archives/Public/www-style/2014Mar/
                    0209.html
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Animations
          Assignee: dino@apple.com
          Reporter: galineau@adobe.com
        QA Contact: public-css-bugzilla@w3.org
                CC: cmarrin@apple.com, eoconnor@apple.com, smfr@me.com

>From Daniel:

"On a similar note, the keyText attribute of CSSKeyframeRule is
read/write. That means it is possible to programmatically assign a
CSSKeyframeRule's key to an existing key in the parent
CSSKeyframesRule... Section 6.2.2 of the spec does not say what happens
in that case and I think it should. In particular, what happens:

- if the assigned keyText is invalid ; should it throw anything?
- if the assigned keyText already exists

Same thing about CSSKeyframeRule.appendRule(). If the key specified by 
the passed string already exists in cssRules, I suppose the existing 
Keyframe should be deleted. This is not specified in the current ED."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 12 March 2014 23:40:00 UTC