Ian Hickson wrote:
On Fri, 23 May 2008, Olli Pettay wrote:
So I'm not sure the errata for this issue is actually needed.
It seems to me that everyone agrees that insertNode() was always intended
to insert a node _into_ the range, and that the collapsed case was simply
lost between the cracks when the DOM WG was writing the spec (much as was
interaction with mutation events, for instance).
Everyone who? And based on what? I don't see anything in the spec that
suggests that. And as Olli pointed out there is clearly language in the
spec that indicates that the inserted node would be after the range in
the collapsed case.
I guess I'm fine with making the change to the spec, but it would be a
change and not an errata. And if we're making changes anyway, I would
requests that we make NodeIterators behave like TreeWalkers as far as
the returnvalue for the NodeFilter goes. That is both more useful and
easier to implement since it allows more code reuse.
/ Jonas
