- From: Simon Sapin <simon.sapin@exyr.org>
- Date: Thu, 15 Aug 2013 21:34:34 +0100
- To: www-style@w3.org
Le 15/08/2013 21:30, Simon Pieters a écrit : >> As you note, the second solution I proposed is not feasible, hence the >> preferred solution would be to add 'setPropertyValue' and >> 'setPropertyPriority' functions to the CSSStyleDeclaration interface, >> for symmetry & speed. > Another option is to let setProperty(value) i.e. with the second argument > omitted leave the priority alone. This would be a change in behavior, but > the current behavior seems unexpected and is likely to result in buggy > code. Does anyone know if there are pages that would break if > setProperty(value) (or with the property = value; syntax) would*not* > unset !important ? > > Your use case doesn't need setting priority without changing the value, so > we probably don't need to have a method for doing so. A variant of this without the compat risk to to trigger the new behavior when the priority argument is the string "unchanged", or something else unlikely to occur in existing content. -- Simon Sapin
Received on Thursday, 15 August 2013 20:34:59 UTC