W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2013

Re: Making selectors first-class citizens

From: Brian Kardell <bkardell@gmail.com>
Date: Wed, 11 Sep 2013 12:28:42 -0400
Message-ID: <CADC=+jfrkcWgUN8KD8o_M79S_5g_SwVf1HZW2gwDTOv=8eGNUg@mail.gmail.com>
To: James Graham <james@hoppipolla.co.uk>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Wed, Sep 11, 2013 at 12:26 PM, Brian Kardell <bkardell@gmail.com> wrote:

>
> 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.
>

Mozillians, just for example:
https://github.com/x-tag/x-tag/blob/master/dist/x-tag-components.js#L2161

-- 
Brian Kardell :: @briankardell :: hitchjs.com
Received on Wednesday, 11 September 2013 16:29:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:13 UTC