Re: What exactly is the replacement for getDefaultComputedStyle?

>From jQuery's perspective, we'd want both: getDefaultComputedStyle to handle userland code that causes is to currently use the iframe hack (and any other situation where we'd want to fallback to a browser default), and "box: none" for our ".hide()" and ".show()" methods, so that we don't need to resort to storing previous values when hiding. 

Sent from Mailbox

On Wed, Sep  3, 2014 at 01:49 AM, Simon Pieters<>, wrote:
On Tue, 02 Sep 2014 23:07:26 +0200, Boris Zbarsky <> wrote:

> At one point we agreed to add Element.getDefaultComputedStyle to CSSOM  

> to address the "what is the default (user+ua) value for this element for  

> a given CSS property?" use case.


> It looks like it's been removed from CSSOM at some point, but I see  

> nothing replacing it.  Certainly none of the things on  

> cover this use case.  Am I  

> just missing something?


> The lack of such an API is causing libraries like jQuery to rely on  

> weird display:none iframe hacks in an attempt to gather this sort of  

> information.  And even with those hacks, if user/UA stylesheets have  

> media query dependent styles there's no way for them to get correct  

> answers.

Is there interest in implementing box:none to satisfy the use case?


Simon Pieters

Opera Software

Received on Wednesday, 3 September 2014 11:16:26 UTC