- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 14 Sep 2013 11:07:43 +0100
- To: Brian Kardell <bkardell@gmail.com>
- Cc: Ryosuke Niwa <rniwa@apple.com>, WebApps WG <public-webapps@w3.org>
On Sat, Sep 14, 2013 at 4:26 AM, Brian Kardell <bkardell@gmail.com> wrote: > I am not really sure why you feel this way - this piece of the draft is > tremendously stable, and interoperable as anything else. The decision to > make it matches was old and popular. It's not just random joe schmoe doing > this, it's illustrated and recommended by respected sources... For example > http://docs.webplatform.org/wiki/dom/methods/matchesSelector 1) I don't think that's a respected source just yet. 2) When I search for matchesSelector on Google I get https://developer.mozilla.org/en-US/docs/Web/API/Element.matches which reflects the state of things much better. Note that the name matchesSelector has been gone from the standard for a long time now. > So.. Ok to keep prefix working in all browsers, but not just add it? For > the most part, isn't that just like an alias? Depends on the implementation details of the prefixed version. FWIW, I'd expect Gecko to remove support for the prefixed version. Maybe after some period of emitting warnings. We've done that successfully for a whole bunch of things. -- http://annevankesteren.nl/
Received on Saturday, 14 September 2013 10:08:11 UTC