- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 31 Jan 2013 18:22:03 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Mike Sherov <mike.sherov@gmail.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Jan 31, 2013 at 6: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. :( If we ever want to do stuff like the CSSOM Values API that allow for translating between units, we'll need this kind of thing anyway. > I can't find any documentation of what "resolved" values are. That's the term for what getComputedStyle returns. > 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. Yes. ~TJ
Received on Friday, 1 February 2013 02:22:50 UTC