Superseded Selectors API

[dontcallmedom]

Selectors API was published as a Rec in 2013, but its content has since been merged in WHATWG DOM.

Unfortunately, this was not listed in the W3C-WHATWG MoU, so we should explicitly get Director's approval to obsolete it and ask for it to be handled the same way other WHATWG-migrated specs get treated.

[marcoscaceres]

@dontcallmedom, do we need to go through the TAG deprecation process?

[dontcallmedom]

No, since WebApps is (or can be argued to be) the group who produced that spec, it can initiate the request to the Director:

The process of obsoleting, rescinding, or restoring a Recommendation can be initiated [...] from any of the following:

• The Working Group who produced, or is chartered to maintain, the Recommendation.

[marcoscaceres]

Ok, cool. We can do that! :)

[marcoscaceres]

@siusin is on it :) Could you let us know if we need to do anything (e.g., CFC) or whatever.

[LJWatson]

We need to put a CFC to the WG then request the transition.

Looking at the Process, we should probably opt for superseded rather than obsolete, since the API will be superseded by what's in the DOM spec.

The DOM LS/review draft is expected to transition to CR by the end of this month, so we should wait until that happens before putting the CFC out.

[marcoscaceres]

CFC sent. Issue is blocked until the end of the month awaiting working group feedback. However, we can probably make any updates to the document in parallel. According to the process document, "only the name and explanation change" - so pretty plainless.

[marcoscaceres]

The CFC has passed. No objections! 🎉

[siusin]

Level 2 has been retired on 16-04-2020 (a note was added to the SoTD).
Level 1 is pending on AC review.

[marcoscaceres]

Appreciate the update @siusin. Thank you.

[marcoscaceres]

Assuming no complaints, let's close this as done.