[1]
[CITE[Bug 409380 &#8211; '''['''REGRESSION''']''' range.selectNodeContents throws an INVALID_NODE_TYPE_ERR on elements created with document.createElement]] ([CODE[2008-01-06 11:35:37 +09:00]] 版) <https://bugzilla.mozilla.org/show_bug.cgi?id=409380#c22>

> There is a growing feeling that we should have a "Web DOM Core" spec, we could
similarly have a "Web DOM Range" spec.

—— [[Ian Hickson]]

([[名無しさん]])

[2]
[CITE[zcorpan's bookmarks tagged with "dom5core" on del.icio.us]] ([CODE[2008-06-21 21:52:05 +09:00]] 版) <http://del.icio.us/zcorpan/dom5core>
([[名無しさん]])

[3]
[CITE[IRC logs: freenode / #whatwg / 20080806]] ([CODE[2008-08-09 17:58:09 +09:00]] 版) <http://krijnhoetmer.nl/irc-logs/whatwg/20080806#l-72>
([[名無しさん]])

[4]
>>3

> [02:57] <Lachy> ok. well, if no-ones working on it by the time I get Selectors API to CR, then I might pick it up.  

([[名無しさん]])


[5]
[CITE[Web DOM Core]] ([TIME[2008-08-14 21:20:13 +09:00]] 版) <http://simon.html5.org/specs/web-dom-core>

[6] [CITE[IRC logs: freenode / #whatwg / 20090407]] ([TIME[2009-06-14 10:25:02 +09:00]] 版) <http://krijnhoetmer.nl/irc-logs/whatwg/20090407#l-204>

> [07:04] <Hixie> i might be roped into a DOM Range rewrite next year
> [07:04] <Hixie> (there's growing pressure to fix that spec)
> [07:05] <Hixie> (and add new APIs to it for things like rich text editing)
> [07:05] <shepazu> Hixie: arguably, that could be part of DOM4