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

Re: [css-cascade] Naming "value of a declaration", renaming "specified value"

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 24 Jun 2013 16:22:28 -0700
Message-ID: <CAAWBYDD3_h=QW93G8w+txetTnutYQVVHM3k8NkOWvDg-0Yc4hw@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: www-style list <www-style@w3.org>
On Mon, Jun 24, 2013 at 4:14 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Monday 2013-06-24 15:45 -0700, Tab Atkins Jr. wrote:
>> If we don't have a publicly-exposed term, then every single spec that
>> wants to define computed values has to handle the cases where there is
>> no value, or the value is a global keyword.  That's not acceptable,
>
> OK -- that's a good reason to keep a term.
>
> I think we should consider more carefully which terms we want to
> expose to the CSSOM, though, rather than exposing everything that
> there happens to be a term for.

I agree.

~TJ
Received on Monday, 24 June 2013 23:23:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC