Last modified: 2014-11-04 18:01:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74950, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72950 - 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.
VisualEditor: [Regression wmf6]“Uncaught Error: Inserted data is trying to cl...
Status: NEW
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All Windows XP
: Normal major
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-04 15:40 UTC by Ritu Swain
Modified: 2014-11-04 18:01 UTC (History)
7 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
screenshot of JS errors in beta (79.55 KB, image/png)
2014-11-04 15:40 UTC, Ritu Swain
Details

Description Ritu Swain 2014-11-04 15:40:31 UTC
Created attachment 17013 [details]
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.
Comment 1 etonkovidova 2014-11-04 18:01:17 UTC
Confirmed in betalabs Chrome.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links