Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark ElementTraversal Rec as obsolete #4

Open
1 of 3 tasks
marcoscaceres opened this issue May 2, 2019 · 8 comments
Open
1 of 3 tasks

Mark ElementTraversal Rec as obsolete #4

marcoscaceres opened this issue May 2, 2019 · 8 comments

Comments

@marcoscaceres
Copy link

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:

  • not sure

The following implementations of this specification are known:

  • All the browsers, all the XML things, I guess...
@dbaron
Copy link
Member

dbaron commented May 24, 2019

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?

@dbaron
Copy link
Member

dbaron commented May 24, 2019

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 47b86da.)

Does that make sense to you?

@marcoscaceres
Copy link
Author

Superseded makes total sense... specially in this case.

@xfq
Copy link

xfq commented Mar 9, 2020

Related: w3c/webappswg#21

@hober
Copy link

hober commented May 7, 2020

The deadline was last summer. Should this still be open? Can we close this?

@marcoscaceres
Copy link
Author

The specs are still Recommendations... so, this should remain open... maybe it's too many specs to do all at once?

@hober
Copy link

hober commented May 12, 2020

cc @plinss @torgo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants