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

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.

-David

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂

Received on Monday, 24 June 2013 23:14:42 UTC