Re: Making selectors first-class citizens

On Mon, Sep 16, 2013 at 1:32 PM, François REMY
<francois.remy.dev@outlook.com> wrote:
>> 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.

Read the thread more closely - as always, we only suggest dropping
prefixed variants *if possible*.

~TJ

Received on Monday, 16 September 2013 20:36:25 UTC