http://jsfiddle.net/8Pr5H/4/

Step to reproduce:

0. Use Chrome 19.0.1084.52 m

1. Run given small jsFiddle snippet;

2. Go to jsFiddle result pane, and fill something into input element;

3. Click somewere NOT ON document body (e.g. address bar, developer tools console, etc);

Expected result: input element replaced by text typed in, and NO EXCEPTIONS;

Observerd result: input element replaced by text typed in, and exception thrown: "NOT_FOUND_ERR: DOM Exception 8"

IE and Firefox are not affected.

Reason: element emptying algorithm is invoked somewhere in middle of NEXT opertions with the element yielding inconsistent state of 'elem' object at line 5911.

elem.firstChild is already set to new content (if any was produced from NEXT opertions), while physically DOM element is empty.

//Anatoly