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 #96

Open
dontcallmedom opened this Issue Sep 6, 2017 · 6 comments

Comments

Projects
None yet
4 participants
@dontcallmedom
Member

dontcallmedom commented Sep 6, 2017

As far as I can tell, https://www.w3.org/TR/ElementTraversal/ has been incorporated into newer versions of the DOM specs. Can we make it so that the TR page reflects this? (I'm not sure if this means going through the Obsolescence process or something else)

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals Sep 6, 2017

Collaborator

Yes, I think it makes sense to state that this has been superseded through the obsolete rec process. I'll propose a CfC

Collaborator

chaals commented Sep 6, 2017

Yes, I think it makes sense to state that this has been superseded through the obsolete rec process. I'll propose a CfC

@xfq
@LJWatson

This comment has been minimized.

Show comment
Hide comment
@LJWatson

LJWatson Aug 16, 2018

Collaborator

@chaals did this CFC go out? I can't find it, but our CFC can happen in a multitude of places, so I'm probably looking in the wrong place.

@xfq I think it makes sense to wait until the outcome of the W3C/WHATWG negotiations before we take steps to render older versions of DOM Obsolete and/or Superseded.

Collaborator

LJWatson commented Aug 16, 2018

@chaals did this CFC go out? I can't find it, but our CFC can happen in a multitude of places, so I'm probably looking in the wrong place.

@xfq I think it makes sense to wait until the outcome of the W3C/WHATWG negotiations before we take steps to render older versions of DOM Obsolete and/or Superseded.

@LJWatson

This comment has been minimized.

Show comment
Hide comment
@LJWatson

LJWatson Sep 8, 2018

Collaborator

@xfq unless ElementTraversal has been incorporated into both the W3C DOM spec and the WHATWG HTML/DOM spec, in which case the original spec is probably Obsolete either way?

Collaborator

LJWatson commented Sep 8, 2018

@xfq unless ElementTraversal has been incorporated into both the W3C DOM spec and the WHATWG HTML/DOM spec, in which case the original spec is probably Obsolete either way?

@xfq

This comment has been minimized.

Show comment
Hide comment
@xfq

xfq Sep 9, 2018

Contributor

@LJWatson All five attributes of the ElementTraversal interface are in WHATWG DOM and W3C DOM now, so I think it's superseded by the DOM spec.

Contributor

xfq commented Sep 9, 2018

@LJWatson All five attributes of the ElementTraversal interface are in WHATWG DOM and W3C DOM now, so I think it's superseded by the DOM spec.

@xfq

This comment has been minimized.

Show comment
Hide comment
@xfq

xfq Sep 13, 2018

Contributor

Selectors API Level 1 can also be obsoleted/superseded. querySelector and querySelectorAll are now defined in both DOM specs, and the algorithms in 6.4. Processing Selectors are defined in the Selectors spec.

Contributor

xfq commented Sep 13, 2018

Selectors API Level 1 can also be obsoleted/superseded. querySelector and querySelectorAll are now defined in both DOM specs, and the algorithms in 6.4. Processing Selectors are defined in the Selectors spec.

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