W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle()

From: Sebastian Zartner <sebastianzartner@gmail.com>
Date: Fri, 1 Feb 2013 09:33:39 +0100
Message-ID: <CAERejNb0Q6MwO4DvAqr7GNZvhj-X69Y4KkspqxfrVGj64AgE8g@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Mike Sherov <mike.sherov@gmail.com>, "www-style@w3.org" <www-style@w3.org>
Funny, formerly you just ignored my requests[1][2] for this, Boris.
I'm happy to see that the discussion about this finally goes into the right
direction.

Sebastian

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=626359#c0
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=573967#c11


On Fri, Feb 1, 2013 at 3:17 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 1/31/13 9:02 PM, Mike Sherov wrote:
>
>> I believe the proposal is a bit broader, but I'll take any interest :-)
>> I believe is what we're talking about, so you can get "used",
>> "computed", "specified", "resolved", "actual", "initial", "default" or
>> any other value type for a CSS property or an element
>>
>
> I see.
>
> Getting used values is, in many cases, pretty painful.  Gecko, for
> example, doesn't really store it in many cases; there would need to be
> special code to recompute it.  Even the bits we already have to do for
> getComputedStyle are bad enough.  :(
>
> Actual values might be even worse (e.g. the actual color value is not even
> under the UA's control; it depends on your monitor hardware, if I
> understand the definition of "actual value").
>
> Computed and specified are totally worth doing.
>
> I can't find any documentation of what "resolved" values are.
>
> Initial and default values ought to be reasonably easy to do, I'd think;
> they're really a special case of specified values with not all rules taken
> into account at heart.
>
> -Boris
>
>
Received on Friday, 1 February 2013 08:34:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT