25035 2014-03-12 23:39:59 +0000 [om] The side-effects of programmatically duplicating a rule key are undefined 2014-10-31 22:38:17 +0000 1 1 1 Unclassified CSS Animations unspecified All All RESOLVED FIXED http://lists.w3.org/Archives/Public/www-style/2014Mar/0209.html P2 normal --- 1 galineau galineau cmarrin eoconnor smfr public-css-bugzilla oldest_to_newest 102284 0 galineau 2014-03-12 23:39:59 +0000 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." 103241 1 galineau 2014-04-01 17:23:53 +0000 Follow up at http://lists.w3.org/Archives/Public/www-style/2014Mar/0517.html 106949 2 galineau 2014-05-28 21:45:24 +0000 Throw syntax error per WG resolution from 2014-04-02 [1]: RESOLVED: Keytext on setting invalid value should throw an error. [1] http://lists.w3.org/Archives/Public/www-style/2014Apr/0016.html 114405 3 galineau 2014-10-31 22:38:17 +0000 Per WG resolution [1], appendRule always appends a valid rule at the end of the @keyframes rule. The rule's key is not considered. [1] http://log.csswg.org/irc.w3.org/css/2014-10-27/#e484268