On Thu, 1 Apr 2010, L. David Baron wrote: > On Thursday 2010-04-01 23:10 -0700, wha...@whatwg.org wrote: > > [giow] (0) The CSS rules need to do attribute value matching consistently > > across HTML and XHTML, despite the rules for interpreting author style > > sheets. > > Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9335 > > > + <p id="case-sensitive-selector-exception">For the purpose of the > > + rules marked "case-sensitive", user agents are expected to use > > + case-sensitive matching of attribute values rather than > > + case-insensitive matching, regardless of whether a case-insensitive > > + matching is normally required for the given attribute.</p> > > + > > + <p id="case-insensitive-selector-exception">Similarly, for the > > + purpose of the rules marked "case-insensitive", user agents are > > + expected to use <span>ASCII case-insensitive</span> matching of > > + attribute values rather than case-sensitive matching, even for > > + attributes in XHTML documents.</p> > > + > > + <p class="note">These markings only affect the handling of attribute > > + <em>values</em>, not attribute names or element names.</p> > > Making attribute values case-insensitive in XHTML seems incompatible > with longstanding Gecko behavior (though our handling of input's type > attribute is buggy, at least) and with the clear intent of XHTML1, and > doesn't seem implementable on top of a conformant CSS selectors > implementation.
I've been working under the assumption that we want to eradicate as many differences between XHTML and HTML as possible, and that there's virtually no compatibility constraint on the XHTML side. If this is an area where we should keep the differences, though, I'm quite happy to change the spec accordingly. Do any other browser vendors have opinions here? Are there compatibility constraints I'm not aware of? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'