- From: Glenn Adams <glenn@skynav.com>
- Date: Mon, 4 Mar 2013 10:21:48 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: John Daggett <jdaggett@mozilla.com>, www-style list <www-style@w3.org>
Received on Monday, 4 March 2013 17:22:38 UTC
On Wed, Feb 27, 2013 at 3:15 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > On Wed, Feb 27, 2013 at 5:58 AM, John Daggett <jdaggett@mozilla.com> > wrote: > > As was decided at the last F2F, cascading variable properties are > > referenced via a case-sensitive ident. However, the definition of > > object model methods referred to in the CSS Variables spec such as > > setProperty, lookup property values with a case *insensitive* lookup. > > That needs to be tweaked for the variables case. > > > > In other words, the two lines below return different values: > > > > a = styleObj.getPropertyValue("var-foo"); > > b = styleObj.getPropertyValue("var-FOO"); > > > > I think the object model spec just needs to include steps for special > > handling properties that begin with "var-". > > Ah, good catch. Yes, this is something for CSSOM to define, probably. > I can patch it *in* Variables, but it would be better done in CSSOM, > I think. > > Alternately, the get/set/etc algorithms can define a flag that > invoking specs can set for CI/CS behavior, and then I can just have > Variables set the flag to CS. That way future specs that need CS > matching for whatever reason can specify this without having to get > CSSOM to update. I'd prefer this. > agreed; see https://www.w3.org/Bugs/Public/show_bug.cgi?id=21190
Received on Monday, 4 March 2013 17:22:38 UTC