Last modified: 2014-08-14 01:39:35 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 T68389, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66389 - VisualEditor: Quickly clicking on "Apply Changes" button multiple times on Media Settings throws console error and cannot make any more changes to any media settings dialog after that
VisualEditor: Quickly clicking on "Apply Changes" button multiple times on Me...
Status: VERIFIED FIXED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Normal minor
: VE-deploy-2014-06-12
Assigned To: Trevor Parscal
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-09 19:24 UTC by Rummana Yasmeen
Modified: 2014-08-14 01:39 UTC (History)
6 users (show)

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


Attachments
Screenshot (187.05 KB, image/png)
2014-06-09 19:24 UTC, Rummana Yasmeen
Details

Description Rummana Yasmeen 2014-06-09 19:24:12 UTC
Created attachment 15609 [details]
Screenshot

Steps to reproduce:

1.Open a page with Image
2.Open the Media Settings dialog
3.Now quickly double click on Apply changes Button

Observed Result:
An error appears in the console:

Uncaught TypeError: Cannot read property 'getSurface' of null
Media Settings dialog for that image and all other images on that page becomes unresponsive.

This is happening in Betalabs and test , not on production(en.wiki)

See the screenshot attached
Comment 1 Gerrit Notification Bot 2014-06-11 22:44:39 UTC
Change 139019 had a related patch set uploaded by Trevor Parscal:
Re-enable apply button in action dialog on close

https://gerrit.wikimedia.org/r/139019
Comment 2 Gerrit Notification Bot 2014-06-11 22:49:01 UTC
Change 139019 merged by jenkins-bot:
Re-enable apply button in action dialog on close

https://gerrit.wikimedia.org/r/139019
Comment 3 Rummana Yasmeen 2014-06-12 17:56:54 UTC
Verified the fix on Betalabs
Comment 4 Rummana Yasmeen 2014-06-13 20:14:04 UTC
Verified the fix on test2
Comment 5 Rummana Yasmeen 2014-06-20 22:15:31 UTC
Verified the fix in production (en.wiki)
Comment 6 Coiby 2014-08-13 02:06:26 UTC
This problem still exist on snapshot 9883566 (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
Comment 7 Coiby 2014-08-13 02:13:32 UTC
(In reply to Coiby from comment #6)
> This problem still exist on snapshot 9883566
> (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).

I just look through the patch, I can't find such file ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.
Comment 8 Roan Kattouw 2014-08-13 02:15:31 UTC
(In reply to Coiby from comment #7)
> (In reply to Coiby from comment #6)
> > This problem still exist on snapshot 9883566
> > (https://extdist.wmflabs.org/dist/VisualEditor-REL1_23-9883566.tar.gz).
> 
> I just look through the patch, I can't find such file
> ve/ui/dialogs/ve.ui.ActionDialog.json in snapshot 9883566.

.js , not .json . Also, try looking for lib/ve/modules/ve/ui/dialogs/ve.ui.ActionDialog.js
Comment 9 Coiby 2014-08-13 02:19:55 UTC
Sorry, it's typo. I mean .js.

There are two files related to Media Seetings dialogue, ve.ui.MWMediaInsertDialog.js and ve.ui.MWMediaEditDialog.js. There's no ve.ui.ActionDialog.js.
Comment 10 Roan Kattouw 2014-08-13 02:22:27 UTC
Right, ActionDialog.js was introduced after the 1.23 release. I thought this bug was introduced after the 1.23 release though, so I'm surprised to hear it's breaking for you.
Comment 11 Coiby 2014-08-14 01:39:35 UTC
(In reply to Roan Kattouw from comment #10)
> Right, ActionDialog.js was introduced after the 1.23 release. I thought this
> bug was introduced after the 1.23 release though, so I'm surprised to hear
> it's breaking for you.

So will the development team resolve this bug for 1.23?

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


Navigation
Links