Last modified: 2014-11-10 16:25:25 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 T75224, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73224 - VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'nodeType' of undefined ,on deleting the content in the Gallery inspector and clicking done
VisualEditor:[Regression wmf7] Uncaught TypeError: Cannot read property 'node...
Status: NEW
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All Windows XP
: Unprioritized normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-10 15:13 UTC by Ritu Swain
Modified: 2014-11-10 16:25 UTC (History)
7 users (show)

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


Attachments
screenshot of JS error (119.38 KB, image/png)
2014-11-10 15:13 UTC, Ritu Swain
Details

Description Ritu Swain 2014-11-10 15:13:44 UTC
Created attachment 17083 [details]
screenshot of JS error

Enviornment- test2, beta

1> Select to insert a gallery. When the inspector opens just type in some text.
2> Now highlight the gallery and click on the gallery context menu. The gallery inspector opens.
3> delete the content in the dialog and then press done.Generates JS error Uncaught TypeError: Cannot read property 'nodeType' of undefined in the console.See screenshot.

Same behavior found in FF 33.1. 
JS error - TypeError: currentNode.children[(nao.offset - 1)] is undefined.
Comment 1 etonkovidova 2014-11-10 16:25:25 UTC
Confirmed -  the error displayed in JS console is exactly as the attached screenshot presents.

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


Navigation
Links