Right. However, it seems at least FF has found a way to do so. Having the "default" keyword would make the task of "default display" even simpler for a dom library like jQuery. .hide() becomes "display: none;" and .show() becomes "remove any inline style, see if display is still none, and if so, set display: default". Of course, css3 display makes the task even simpler: .hide() and .show() just manipulate the "box" property, but having a "default" keyword helps for things like "box-sizing", "font-weight", "margin", "padding", "font-family" and any other property that changes on a per element basis. Having a "default" keyword seems even more important than having an "initial" keyword, despite its complexity. — Sent from Mailbox On Sat, Sep 6, 2014 at 9:30 PM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 09/03/2014 10:59 AM, Boris Zbarsky wrote: >> On 9/3/14, 1:46 AM, Simon Pieters wrote: >>> http://lists.w3.org/Archives/Public/www-style/2013Aug/0161.html >>> http://lists.w3.org/Archives/Public/www-style/2013Aug/0164.html >>> https://dvcs.w3.org/hg/csswg/rev/3b8ded576b8a >> >> I disagree on the use case situation, fwiw. >> >> Especially now that CSS has dropped the ability to declaratively >> say "use the UA+user default style", at least having a way to >> programmatically ask for that style would allow polyfilling... > We dropped it because people said it was hard to implement. > The spec itself was stable, iirc. > ~fantasai
Received on Sunday, 7 September 2014 02:25:03 UTC