1216193 - Implement webkitMatchesSelector

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Boris Zbarsky [:bzbarsky]]

Per https://github.com/whatwg/compat/issues/3

Comment 1

[Boris Zbarsky [:bzbarsky]]

Attachment: Implement webkitMatchesSelector

Comment 2

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Comment on attachment 8675767 [details] [diff] [review]
Implement webkitMatchesSelector

Review of attachment 8675767 [details] [diff] [review]:
-----------------------------------------------------------------

r=me

Comment 3

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/c1a68835d084

Comment 4

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/c1a68835d084

Comment 5

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/c1a68835d084

Comment 6

[Jean-Yves Perrier [:teoli]]

Removing ddn: we don't maintain a list of webkit-prefixed features supported by Gecko (on MDN at least)

Comment 7

[j.j.]

(In reply to Jean-Yves Perrier [:teoli] from comment #6)
> Removing ddn: we don't maintain a list of webkit-prefixed features supported
> by Gecko (on MDN at least)

but
 https://developer.mozilla.org/en/docs/Web/API/Element/matches
could have a little note?

You can argue that prefixes are evil und shouldn't documented, but that's not current practice on MDN.

Comment 8

[Boris Zbarsky [:bzbarsky]]

This isn't even about prefixes being evil, or webkit-prefixed features.  This is not a webkit-prefixed feature at this point.  It's a standard DOM feature (see <https://dom.spec.whatwg.org/#dom-element-webkitmatchesselector>) that happens to have a name starting with "webkit".

Comment 9

[Jean-Yves Perrier [:teoli]]

Oh my bad, misunderstood.