On Wed, 14 May 2008, Olli Pettay wrote:
> > which I believe to be the intent of the specification. This is 
> > implemented by Opera and WebKit already, and is tested by Acid3.
> Gecko does what the current spec says.

All three implementations do what the spec says now -- the spec can be 
interpreted both ways.

> Does web content rely on the current spec behavior?

To my knowledge, very little Web content relies on this spec at all. 
That's why Acid3 tested it, to make it interoperable enough that it could 
be used. :-)

> Did Webkit or Opera change their behavior just to pass ACID3 (but not to 
> follow Range spec)?

I didn't check whether they implemented this before Acid3 or not.

On Wed, 14 May 2008, Boris Zbarsky wrote:
> Ian Hickson wrote:
> > I propose that we change the spec to explicitly say that if you call
> > insertNode() on a collapsed range, the end point offset is increased by one
> Increased at what point in time, exactly?  Specifically, if there is a 
> DOMNodeInserted listener that repositions the range when the node 
> insertion happens, or even mutates the DOM, what is the expected 
> behavior?

DOM2 Range doesn't define anything to this level of detail yet, 
unfortunately. For example regular old insertions and deletions near 
ranges cause changes to the range values but the spec doesn't say if this 
is before or after the events.

It seems that for sanity we should say it happens before, if we specify 
this. Should we do this as a separate errata?

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Reply via email to