> I guess these should be followed in the selector search, and > depending on browsers their should be fallbacks for a 2nd search > without the toLowerCase or something...
For a given Fx.Morph(selector) and selectorText that *solely* differ by the case of their type selectors, applying the same "massage" of the type selectors on both sides before doing the string comparison would solve that, without a need for a separate sweep. *But* there are enough other cross-browser diffs that Fx::CSS::Search wouldn't be totally fixed up by that modification, as you can see in the second ticket and also elsewhere on the web. I would stick to single class selectors in ::Morph (even groups of selectors like '.classone, .classtwo' will also not work cross-browser). -- Sandy
