This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23691 - Drop nextElementSibling from DocumentType
Summary: Drop nextElementSibling from DocumentType
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ms2ger
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-31 16:41 UTC by Anne
Modified: 2013-11-17 10:08 UTC (History)
9 users (show)

See Also:

Attachments

Description Anne 2013-10-31 16:41:17 UTC 
Per https://bugzilla.mozilla.org/show_bug.cgi?id=932501 and https://code.google.com/p/chromium/issues/detail?id=246609 the world sucks.

Anyone any bright ideas, last words?
Comment 1 Simon Pieters 2013-11-01 08:44:51 UTC 
It looks like Dojo is being fixed?

Maybe we should remove it now and try to put it back in a year or so?
Comment 2 Anne 2013-11-01 11:50:43 UTC 
If we do that I'm not going to update the specification for now. Pointless: I wish DocumentType never existed to begin with.
Comment 3 Boris Zbarsky 2013-11-01 17:31:46 UTC 
Dojo is fixed.  The problem is stuff shipping with old versions of it, with no incentive to change...  The Oracle Convergence thing is the main example we know of so far.  What makes you think this will stop being a problem in a year?
Comment 4 Boris Zbarsky 2013-11-01 17:32:23 UTC 
And in particular, Dojo has been fixed for a while here, afaict.  So it's not like they just fixed it and people need to update.  They fixed it a longish time ago and people don't update.
Comment 5 Simon Pieters 2013-11-04 08:52:56 UTC 
OK. I'm trying to be optimistic and retain sanity, but yeah. :-(

Should we just remove nextElementSibling or also previousElementSibling?
Comment 6 Erik Arvidsson 2013-11-04 14:44:56 UTC 
FWIW, Chrome has been shipping with this for a while. Yes, it did break things but I believe most of the major sites have fixed their bugs by now.
Comment 7 Boris Zbarsky 2013-11-04 14:52:00 UTC 
Erik, how long is "a while"?

https://bugzilla.mozilla.org/show_bug.cgi?id=932501 certainly says that things are broken there in Chrome.
Comment 8 Erik Arvidsson 2013-11-04 15:10:29 UTC 
(In reply to Boris Zbarsky from comment #7)
> Erik, how long is "a while"?

Since August (M29)
 
> https://bugzilla.mozilla.org/show_bug.cgi?id=932501 certainly says that
> things are broken there in Chrome.

Updated the bug.
Comment 9 Anne 2013-11-14 02:06:13 UTC 
So bz is going to remove it from Gecko as well as previous* by putting them on a new NonDocumentTypeChildNode interface as he doesn't consider the breakage tolerable. If Chrome wants to continue their experiment in getting these sites fixed I'd be happy to back that with the specification. Meanwhile I'll leave this open so we can check again in a year or so.
Comment 10 Boris Zbarsky 2013-11-14 02:35:03 UTC 
I strongly feel we should remove known-not-web-compatible things from the spec so we don't create attractive nuisances for people trying to use the spec to implement things but not following along with every bug report.

If at some point we think this might be web-compatible, _that_'s when we add it back.