- From: Sylvain Galineau <galineau@adobe.com>
- Date: Wed, 12 Mar 2014 23:40:30 +0000
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style <www-style@w3.org>
On 3/11/14, 3:26 AM, "Daniel Glazman" <daniel.glazman@disruptive-innovations.com> wrote: >The spec says about CSSKeyframesRule.deleteRule(): > > ...deletes the CSSKeyframeRule with the passed key. > >But the spec explicitely allows multiple keyframe rules for same key, >saying that in that case the last one specified wins. > >Then I assume only the last one specified for a given key is preserved >in the OM. I think it should noted somewhere. I have filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=25034 for this issue. > >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. I have filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=25035 for this issue. To be continued fairly soon. Thanks.
Received on Wednesday, 12 March 2014 23:41:03 UTC