W3C home > Mailing lists > Public > www-style@w3.org > September 2014

Re: What exactly is the replacement for getDefaultComputedStyle?

From: Mike Sherov <mike.sherov@gmail.com>
Date: Thu, 04 Sep 2014 05:26:17 -0700 (PDT)
Message-Id: <1409833576396.aa24e2c9@Nodemailer>
To: "Simon Pieters" <simonp@opera.com>
Cc: "Boris Zbarsky" <bzbarsky@mit.edu>, "www-style list" <www-style@w3.org>
IMO, putting back GetStyleUtils#defaultStyle seems best. This would also help distinguish between elements that are border-box by default and elements that are content-box by default, which happens when devs (e.g.) use an opinionated framework like Bootstrap which does a global border-box reset.


I'm sure I can continue finding useful examples for various properties. 
—
Sent from Mailbox

On Thu, Sep 4, 2014 at 4:03 AM, Simon Pieters <simonp@opera.com> wrote:

> On Wed, 03 Sep 2014 16:59:57 +0200, Boris Zbarsky <bzbarsky@mit.edu> 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...
>>
>>> Is there interest in implementing box:none to satisfy the use case?
>>
>> That's blocked on there being a stable spec on box:none, and then on  
>> implementing the resulting complexity.  Said complexity is much higher,  
>> at first glance, than that of getDefaultComputedStyle.
> OK. Should I put back GetStyleUtils#defaultStyle ? Or do we want something  
> more lightweight that only supports the 'display' property?
> -- 
> Simon Pieters
> Opera Software
Received on Thursday, 4 September 2014 12:26:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:46 UTC