Last modified: 2014-07-08 23:05:37 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 T63968, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61968 - VisualEditor: Image resizing handlers appear on all four corners (not just one / two) if image is in another image's caption editor
VisualEditor: Image resizing handlers appear on all four corners (not just on...
Status: VERIFIED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
: 62283 (view as bug list)
Depends on:
Blocks: ve-mediasupport
  Show dependency treegraph
 
Reported: 2014-02-26 23:14 UTC by Rummana Yasmeen
Modified: 2014-07-08 23:05 UTC (History)
9 users (show)

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


Attachments
screenshot (48.09 KB, image/png)
2014-02-26 23:24 UTC, Rummana Yasmeen
Details

Description Rummana Yasmeen 2014-02-26 23:14:21 UTC
Steps to reproduce:

1.Open a page with VE
2.Insert an image
3.Go to Media Settings of that image
4.Insert another image inside it in the General Settings section
5.Go to Media Settings for that image and set the Image type as Frameless and keep the position to right

Observed Result:
The image resize handlers appear at all four corners instead of appearing only at bottom left corner

See the screenshot attached

Test Environment: http://en.wikipedia.beta.wmflabs.org/
Browser: Chrome Version 26.0.1410.65 
OS: MAC OS X 10. 8. 5
Comment 1 Rummana Yasmeen 2014-02-26 23:24:18 UTC
Created attachment 14695 [details]
screenshot
Comment 2 James Forrester 2014-07-08 20:20:03 UTC
*** Bug 62283 has been marked as a duplicate of this bug. ***
Comment 3 James Forrester 2014-07-08 20:21:29 UTC
This appears to now be fixed.
Comment 4 Rummana Yasmeen 2014-07-08 23:05:37 UTC
yes, now it is fixed.

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


Navigation
Links