- From: L. David Baron <dbaron@dbaron.org>
- Date: Mon, 17 Dec 2012 15:35:18 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-archive@w3.org
On Friday 2012-12-07 09:11 -0800, Tab Atkins Jr. wrote: > On Wed, Dec 5, 2012 at 11:02 PM, L. David Baron <dbaron@dbaron.org> wrote: > > There are two references to the term "component value" that have > > crept back in to the css-variables editor's draft since the last > > working draft. I thought we'd agreed (multiple times, I think) that > > this wasn't the approach we were taking. Instead, we are using > > token stream substitution, because it is possible to describe in a > > way that can lead to interoperable implementations without > > all-but-one of the implementations having to rewrite. > > > > In particular, I'd suggest replacing: > > # A variable can be used in place of any component value in any > > # property on an element. > > with: > > # A variable can be used in place of any part of a value in any > > # property on an element. > > > > and replacing: > > # Similarly, you can't build up a single component value where > > # part of it is provided by a variable: > > with: > > # Similarly, you can't build up a single token where part of it is > > # provided by a variable: > > Sorry, force of habit. These are good changes. Could I ask that you make them sooner rather than later? (Or would you like me to do so?) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂
Received on Monday, 17 December 2012 23:35:46 UTC