Page MenuHomePhabricator

VisualEditor: Prevent drag and drop of non-media content using monobook skin in Firefox
Closed, ResolvedPublic

Description

(Tested on Firefox 22, Monobook skin)

Steps to reproduce

  • Go to the "The Damned Thing (short story)" page and edit it with the visual editor.
  • Go to the "Gothic elements" selection, and select all the text from "Gothic elements" (Header) to "inadequate." (Last word of the section). This should also select the image.
  • Click and drag the entire section, and drop it of before the "Analysis" section (Just drop it right before the A in that word, make sure the text entry | is displayed. The image itself will be gone. But for the fun part: Click anywhere on the editing canvas text.

Suddenly, your entire input screen will be white. What seems to happen is that the image is blanked (Replaced by a white square) and plastered full size all over the page. You can try to drag it away, but each time you try it will replace itself over the pages content.

https://en.wikipedia.org/wiki/File:Visual_Editor_-_Giant_White_Image.png contains a screenshot of the problem.


Version: unspecified
Severity: major
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=50643

Details

Reference
bz50721

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:42 AM
bzimport added a project: VisualEditor.
bzimport set Reference to bz50721.

Drag and drop should be disabled, but cant find the bug for it.

I cant reproduce the problem at the mentioned page on Firefox 22 (Win or Linux) using Vector, but goodness me I can reproduce this when I use monobook skin.

https://en.wikipedia.org/wiki/The_Damned_Thing_%28short_story%29?veaction=edit

(page hasnt changed since the bug was raised :/)

Drag and drop is disabled for only text content, however drag and drop is allowed (in monobook) when an image and something else are selected, and the result is nasty.

I think this duplicates bug 50643

Chris: Good catch, thanks for finding that!

  • This bug has been marked as a duplicate of bug 50643 ***