Remove mozMatchesSelector

NEW
Unassigned

Status

()

Core
DOM
3 years ago
2 years ago

People

(Reporter: Ms2ger, Unassigned)

Tracking

(Blocks: 1 bug, {dev-doc-needed, site-compat})

Trunk
dev-doc-needed, site-compat
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
We might want to warn first.
(Reporter)

Updated

3 years ago
Blocks: 775235
Keywords: dev-doc-needed
This is not very viable anytime in the foreseeable future due to the slow W3C action on this API and the bikeshedding that was involved.

For example, jQuery versions before 2.1.1 and 1.11.1 have code like this:

	if ( (support.matchesSelector = rnative.test( (matches = docElem.webkitMatchesSelector ||
		docElem.mozMatchesSelector ||
		docElem.oMatchesSelector ||
		docElem.msMatchesSelector) )) ) {

and will fall back to something slower if none of those are defined.  So until all sites using jQuery update to 2.1.1/1.11.1 or newer, we're sort of stuck with mozMatchesSelector.

Adding the warning might help, since at least all sites using the old library versions will warn....

Updated

3 years ago
Keywords: site-compat
webkitMatchesSelector is also very popular, foolip has opened an issue on the compat spec for it. Blink won't be removing it for a very long time, if ever: https://github.com/whatwg/compat/issues/3
Once bug 1216193 lands, we can probably do this.  Just need to remove chrome/extension uses....
I'll write patches for the chrome/extension uses, there aren't that many.
Depends on: 1216260
Depends on: 1216262
Posted the site compatibility doc: https://www.fxsitecompat.com/en-US/docs/2015/element-mozmatchesselector-will-be-removed/
You need to log in before you can comment on or make changes to this bug.