Open marcoscaceres opened 5 years ago
This issue was originally filed here: https://github.com/w3c/WebPlatformWG/issues/96
It also suggests obsoleting the whole DOM family:
New implementations should follow the following specifications:
The deadline for the TAG to act without this going directly to AC review is 2019-07-31 at 09:17 UTC.
I'd note that it is probably better to batch multiple requests in a single AC review, so if you think it's worth requesting obsoletion for more of them, it's likely worth doing at the same time.
Is all of the material in the ElementTraversal REC also in the DOM specification, or are there parts that were removed due to lack of implementation?
Also, I realize we failed to update the template when the Superseded status was added to the process.
I'm inclined to think we should consider this as a request for marking the spec as Superseded rather than as Obsolete. (I just did that in https://github.com/w3ctag/obsoletion/commit/47b86dafb11af790a8a7a36737bae8ada6be5e42.)
Does that make sense to you?
Superseded makes total sense... specially in this case.
The deadline was last summer. Should this still be open? Can we close this?
The specs are still Recommendations... so, this should remain open... maybe it's too many specs to do all at once?
cc @plinss @torgo
Hello TAG!
I'm requesting that the TAG consider the following specification
be considered by the TAG for (choose one):
It's now part of DOM spec.
This specification was produced by (Old) Web Applications (WebApps) Working Group which was closed on 2016 (?).
The following specifications have dependencies on this specification:
The following implementations of this specification are known: