Open Bug 413406 Opened 17 years ago Updated 4 years ago

incorrect drag-and-drop behaviour in designmode

Categories

(Core :: DOM: Editor, defect, P5)

x86
Windows XP
defect

Tracking

()

People

(Reporter: cap, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 Browse to http://wwwiuk.informatik.uni-rostock.de/~cap/bugzilla/test.html Position mouse over the browser field. The caret should be blinking in line 1 before the S. In this situation, hit return four times. Select the "me" of "Some text" with the mouse. You cannot drag the me to line 4, only to lines 1, 2 or 3 - the caret only shows in lines 1, 2 or 3. If you drop the text with the caret showing in line 3 the text is not placed at the position of the caret in line 3 but in the next line, which is line 4. Play around a bit with selecting text portions and dropping them on empty lines. The behaviour is not what you expect, ie. the text is dropped on different lines than the one having the caret. Reproducible: Yes Reproducible with: Firefox 2.0.0.11 Reproducible with: Firefox 3.0b2 Reproducible: Always Expected Results: The dropped text should appear exactly where the caret is (and not in the next line). Probably due to a drop which happens after a break and thus understandable as an effect - but wrong from an intuitive GUI point of view.
Version: unspecified → Trunk
Component: General → Editor
Product: Firefox → Core
QA Contact: general → editor
Blocks: 424615
This is still happening in [Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008041710 Minefield/3.0pre]
Status: UNCONFIRMED → NEW
Ever confirmed: true

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.