- From: François REMY <francois.remy.dev@outlook.com>
- Date: Fri, 1 Feb 2013 21:11:03 +0100
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>
- CC: "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
<sorry, I forgot to include the links> > > What I'm not convinced about is an API that has a polymorphic "immutable > > string or live object" return type, because that seems like a footgun (e.g. > > saving the return value and then checking it later has different behavior > > depending on which flavor of the API you managed to call). > > > > David's proposed API does not have that problem. > > Yeah, I like David's API a lot. > Me too, FWIW. It reminds me of 'style', 'runtimeStyle' and 'currentStyle' of IE. BTW, while we are at it, it's maybe the good time to support the 'override' style level (more or less 'runtimeStyle' of IE)? It allows to style a pseudo element directly but the implementation is a stub in webkit (returns null) and is not implemented in any other browser (IE's runtimeStyle is not able to target pseudo elements). http://stackoverflow.com/questions/9798210/is-there-any-way-to-reset-after-before-css-rules-for-an-element http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-DocumentCSS
Received on Friday, 1 February 2013 20:11:32 UTC