Re: Making selectors first-class citizens

On Sep 11, 2013 11:11 AM, "James Graham" <james@hoppipolla.co.uk> wrote:
>
> On 11/09/13 15:50, Brian Kardell wrote:
>
>> Yes, to be clear, that is what i meant. If it is in a draft and
>> widely/compatibly implemented and deployed in released browsers not
>> behind a flag - people are using it.
>
>
> If people are using a prefixed — i.e. proprietary — API there is no
requirement that a standard is developed and shipped for that API. It's
then up to the individual vendor to decide whether to drop their
proprietary feature or not.
>
>

Please note carefully what i said.  I don't think I am advocating anything
that hasn't been discussed a million times.  In theory what you say was the
original intent.  In practice, that's not how things went.  Browsers have
changed what used to be standard practice to help avoid this in the
future.  We are making cross-browser prollyfills outside browser
implementations to avoid this in the future.  What is done is done though.
The reality is that real and not insignificant production code uses
prefixed things that meet the criteria I stated.  If removed, those will
break.  If something with the same name but different signature or
functionality goes out unprefixed, things will break.