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.

Sign up for GitHub

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

Jump to bottom

"The previousElementSibling and nextElementSibli..." #210

Closed
senolv opened this issue Apr 8, 2016 · 9 comments
Closed

"The previousElementSibling and nextElementSibli..." #210

senolv opened this issue Apr 8, 2016 · 9 comments

Comments

@senolv
Copy link

senolv commented Apr 8, 2016

https://dom.spec.whatwg.org/#interface-nondocumenttypechildnode

The previousElementSibling and nextElementSibling attributes have been removed from DocumentType nodes for compatibility reasons. If these additions are deemed compatible enough in the future, they could be reinstated.

If there wasn´t a compability problem, in which interface would they both be listed? Node or Element?
@domenic
Copy link
Member

domenic commented Apr 8, 2016

ChildNode

@senolv
Copy link
Author

senolv commented Apr 8, 2016

Thanks

@ArkadiuszMichalski
Copy link
Contributor

And bug for this:https://www.w3.org/Bugs/Public/show_bug.cgi?id=23691
On the occasion, is there any approximate time when this incompatybile problem will be checking again or we stuck with this interface forever?

@annevk
Copy link
Member

annevk commented Apr 8, 2016

We should probably just suck it up and just note they can't be put on DocumentType.

@senolv
Copy link
Author

senolv commented Apr 9, 2016

that would be more appropiate, when they belong to ChildNode.

The more Objects you create, the more you confuse.

The same matter with NonElementParentNode, no sry, it´s not the same, it´s harder to comprehend.

Instead of just mentioning that there are compability conflicts with jquery´s old versions, you create a new object and say, this interface will be removed and its method will be an attribute of ParentNode when jquery...

What I try to say is, when anyone is interested in dom standarts jquery is not important enough to be the reason to make me wait for the time when a core-tech dominates a framework.

I´m sry for my bad language, it´s late in the night, hope you could catch my thoughts

@annevk
Copy link
Member

annevk commented Apr 9, 2016

It's harder to comprehend to have multiple mixins, sure, but we cannot actually change any of this. We can just clarify that it will remain this way since it's unlikely to become that much less of a problem.

@ArkadiuszMichalski
Copy link
Contributor

We should probably just suck it up and just note they can't be put on DocumentType.

My guess is that the same will happen to NonElementParentNode? Comparing to other
potential changes (Attr, CDATASection, Documnet) this comment looks so pessimistic, but to be sure I ask again for another 3 years:)

@annevk
Copy link
Member

annevk commented Apr 10, 2016

Yeah, we should update both and indeed add back some of the ancient features. It's pretty clear that browsers are not going to remove them. It's just not worth the amount of churn it turns out.

@annevk
Copy link
Member

annevk commented Apr 15, 2016

Thanks for reporting this @senolv!

@annevk annevk closed this as completed in 346e32c Apr 15, 2016
tabatkins added a commit to tabatkins/dom that referenced this issue Apr 28, 2016
@tabatkins
sync upstream (#1)
11dfa6e 
* Add more legacy event types for createEvent()

Approximately as requested at
https://bugzilla.mozilla.org/show_bug.cgi?id=1251198#c7. This is the
list of events supported in createEvent() by at least two of Firefox,
Chrome, and IE 11. The one exception is I omitted MutationEvent,
which all three support, because apparently spec-land has decided to
deny its existence in the hope that it will go away.

Bikeshed does not know about all of the added interface names,
hopefully that will sort itself out over time.

* Meta: improve pull request instructions for DOM

See whatwg/fetch#276 for context.

* Enable an event listener to be invoked just once

* Editorial: web compatibility typically remains relevant

Fixes whatwg#210.

* Shadow: define attachShadow() for custom elements

* Meta: make it easier to reference participate in a tree

PR: whatwg#216

* Define node document for new Text nodes

Fixes whatwg#224 and part of whatwg#212. Also fix part of whatwg#209 by stating these
algorithms can rethrow exceptions.

* Use a single concept for attribute changes

This setup is still a little sketchy I think, but not more so than the
insertion and removing steps.

* SVGEvent is only Gecko, Blink also has SVGEvents

As pointed out by zcorpan in whatwg#227.

* Set createDocument()'s content type based on namespace

Fixes whatwg#217.

PR: whatwg#218

* Make document.createEvent("touchevent") sometimes throw

Browsers typically disable touch events on non-touch devices, and there exists web content that detects this difference using document.createEvent().

Fixes whatwg#227.

* Shadow: define slotchange event

Shadow: define slotchange event

Fixes WICG/webcomponents#288.

This defines the slotchange event in response to remove/insert operations, changes to a slot’s name attribute, and changes to an element’s slot attribute.

This also introduces the assigned nodes concept for slots, and assigned slot concept for slotables.

Slotables now also have a name, rather than a “get name”.

The slotchange event dispatches just after mutation observers have their callbacks invoked. The slotchange event is not yet marked scoped as scoped events are not yet defined in the DOM Standard.

Note: although the original issue did not mention it, this also suppresses signaling when slots are removed from a tree. Not just when they are inserted.

* Editorial: update custom element cross-spec references

* Editorial: fix a few cross-linking missteps

* Editorial: make "is" and "prefix" optional in "create an element"

* Use "create an element" in createHTMLDocument

Takes care of part of whatwg#212.

* Editorial: align exception language with IDL

* Editorial: introduce more shadow-including terms for CSS

Fixes whatwg#225.

* Editorial: distributed -> flattened

* Meta: export more terms

Fixes whatwg#233.

* Editorial: add "shadow host" and "assigned" as terms

This makes a couple of non-null checks read better and enshrines a term
we had already been using.

* Editorial: flip non-null/otherwise conditions

PR: whatwg#234

* Shadow: <slot> is now defined in HTML

* Remove passive as event listener key

This changes makes passive no longer contribute to the uniqueness of
an event listener. It therefore also no longer needs to be supported
as part of removeEventListener().

Fixes WICG/EventListenerOptions#27.

PR: whatwg#236

* Meta: point out event's timeStamp is likely to change

See whatwg#23 for details.

* Add [CEReactions] annotations to mutating methods

Part of WICG/webcomponents#186, and furthering whatwg/html@27aa7bc.

Linking [CEREactions] will happen once speced/bikeshed#677 is fixed.

* Editorial: check stop propagation flag at start of invoke

* Editorial: deduplicate Veli Şenol

* Editorial: define defaults for EventListenerOptions

Although this is also done in prose, this nonetheless simplifies the
prose a bit and makes it clearer to those skimming the standard what is
going on (although skimming is not recommended).

Fixes whatwg#239.

* Meta: link to Japanese translation

See
triple-underscore/triple-underscore.github.io#1
for more details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@domenic @annevk @ArkadiuszMichalski @senolv