Is reparenting a gotcha?

[jakearchibald]

In the common case, each ParserChunk will be addressing a new node, but in the event of a parser error a ParserChunk may be used to move an existing node.

I'm worried that developers won't code expecting this, and end up with weird bugs as a result.

We could add a boolean to the ParserChunk to indicate that the node isn't new. The idea is this will increase the likelihood that developers will handle that possibility.

[jakearchibald]

cc @domenic.

[domenic]

Adding the boolean feels unnecessary to me over just documenting it. (And having a do-the-right-thing DOMWritable sink.)

But, I think we should keep this open to track any instances of the problem occurring, especially once we get more hands-on experience.