Race condition in Chrome 19 in element.text() [more specifically element.empty()] when focus leaves body

[aar.now@…]

​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

[dmethvin]

This sounds like a Chrome error that we cannot fix. Have you reported the problem to the Google Chrome team?

[artazor]

Hmm... seems that it is related to jQuery interacting with bubbling of focusout. Because without bubbling it works just fine: ​http://jsfiddle.net/8Pr5H/5/

The same steps yield no error.

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!