- From: Anne van Kesteren <annevk@opera.com>
- Date: Sun, 14 Feb 2010 12:21:19 +0100
- To: "Sylvain Galineau" <sylvaing@microsoft.com>, "CSS WG" <www-style@w3.org>
On Fri, 12 Feb 2010 21:30:51 +0100, Sylvain Galineau <sylvaing@microsoft.com> wrote: > I agree this seems better, and likely least surprising to the caller. I > was mostly wondering whether the 'shorthandedness' of the properties was > the only criteria in this list. It is, yes. >> Right, it is the computed value as defined by CSS 2.1. Maybe I should >> simplify the introduction by stating that for some properties it does >> something different for historical reasons, without trying to go into >> detail. > > Right. I don't mean to be slow but I want to make sure I got it right. > As I read it the spec says getComputedStyle() shall return one of: > 1. Nothing (modulo earlier comment) > 2. The property's used value > 3. the property's computed value as defined by CSS2.1 > > Thus all the properties that fall in #2 are the ones who have > historically diverged from CSS2.1 > 's definition of computed value, right ? Yes. -- Anne van Kesteren http://annevankesteren.nl/
Received on Sunday, 14 February 2010 11:22:01 UTC