VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to close the root node (at index 0)” when applying heading formats with language inspector open.
Open, NormalPublic

Description

screenshot of JS errors in beta

Environment- test2, beta

1> In a blank page, open the Language inspector.
2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
2> The inspector closes and you see the language context menu.
3> type in some text, it doesn’t take the language annotation(looks like plain paragraph text)
4> Hit enter and JS error “Uncaught Error: Inserted data is trying to close the root node (at index 0)”. See screenshot.
5> Notice no matter where your cursor is on the page, the language context menu never moves from its place or closes for a new line.

In beta an additional JS error appears at step#2, “Uncaught Error: Offset could not be translated to a DOM element and offset: 2”.

Reproducible in FF too.


Version: unspecified
Severity: major
OS: Windows XP

Attached:

Details

Reference
bz72950
bzimport raised the priority of this task from to Normal.
bzimport set Reference to bz72950.
Swainr created this task.Nov 4 2014, 3:40 PM

Confirmed in betalabs Chrome.

I can't reproduce this.

I could not reproduce it either.But I did get the JS error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” and the text typed was just plain paragraph-like.

Here are the steps-:

Environment- test2, beta

1> In a blank page, open the Language inspector.
2> While the inspector is open ,select any Heading format from the drop-down,for ex- select Heading.
3> The inspector closes and you see the language context menu.
4> Type some text, it doesn’t take the language annotation(looks like plain paragraph text).JS error “Uncaught Error: Offset could not be translated to a DOM element and offset: 2” appears.

See the screencast at http://youtu.be/qXID9SlMClo

{F27349}Screenshot of the JS Error "Offset could not be translated to a DOM element and offset: 2".

Isn't that already reported as T76717?

Yes, it is.
Here, I was also pointing at the typed text appearing plain, i.e., without any language annotation.