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

Resolved values, by definition, is what getComputedStyle returns. For
width,height, and the other box properties, if display is none, used
value... Otherwise computed. It's in the CSSOM spec.

The cases I'm most interested in, in the moment is getting back "auto"
or an actual number for "margin", "top", and "left".

We don't need to implement them all just yet, but having a flexible
signature that allows you to specify value type is nice.

Mike Sherov
Lead Developer
SNAP Interactive, Inc.
http://snap-interactive.com
http://areyouinterested.com
Ticker: STVI

Sent From Mobile: Please excuse my grammar, tone, and punctuation. My
thumbs can't produce flowery prose.

On Jan 31, 2013, at 9:17 PM, 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 02:30:10 UTC