RE: Making selectors first-class citizens

> Regardless of what they assumed, there's presumably a case to handle
> older browsers that don't support it at all. If the scripts guessed
> wrongly about what the unprefixed name would be, then they'll fall
> into this case anyway, which should be okay.
>
> If they didn't support down-level browsers at all, then they're
> already broken for a lot of users, so making them broken for a few
> more shouldn't be a huge deal. ^_^

I can't name any currently-used mobile browser that doesn't ship with a *MatchesSelector function. The "drop it" proposal is to break code for the sake of breaking code. What is the point? We will soon have querySelector and query, and that didn't make the world fall into pieces... 		 	   		  

Received on Monday, 16 September 2013 20:33:26 UTC