Last modified: 2013-07-04 01:36:15 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 T52682, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50682 - VisualEditor: "Undo" of image resizing causes wonky displacement
VisualEditor: "Undo" of image resizing causes wonky displacement
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: High normal
: VE-deploy-2013-07-04
Assigned To: Christian Williams
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-03 18:17 UTC by Maggie Dennis
Modified: 2013-07-04 01:36 UTC (History)
4 users (show)

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


Attachments

Description Maggie Dennis 2013-07-03 18:17:22 UTC
From English Wikipedia:

'''Steps to reproduce:'''
* Edit the [[Vogrie House]] article in the visual editor.
* Resize the image. Larger or smaller doesn't matter.
* Press either CTRL + Z, or undo the edit using the undo button. 

Instead of undoing the edit, it suddenly enlarges the image object. The image is placed in the center of the screen, and the object itself even overlaps the main navigation in the Mono interface. Of course as always: Firefox 22 used to test this. [[User:Excirial|<font color="191970">'''Excirial''']]</font><sup> ([[User talk:Excirial|<font color="FF8C00">Contact me</font>]],[[Special:Contributions/Excirial|<font color="FF8C00">Contribs</font>]])</sup> 18:03, 3 July 2013 (UTC)

See screenshot:
http://en.wikipedia.org/wiki/File:VisualEditor_-_Undoing_a_resize_issue.png

I tried on Chrome on a Mac, and it didn't work there, either, but instead shoved the image to the left of the screen
Comment 1 James Forrester 2013-07-04 01:36:15 UTC
We've now fixed this, and deployed it; sorry for the issue.

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


Navigation
Links