196065 - Cannot drag and drop text to the tab bar.

Status: VERIFIED WORKSFORME

(Core :: DOM: Copy & Paste and Drag & Drop, defect)

Description

[Jason Bassford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030305
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030305

Rather than re-open bug 185033 I'm filing a new bug since I believe the reasons
for the breakage are different.  I also noticed this a little while ago, but
could have sworn somebody else filed a bug - but I can't find it.

Symptoms:

1. Text from text boxes can no longer be dragged and dropped anywhere.  (Drag
doesn't start.)

2. Text from page content can no longer be dragged and dropped onto the tab bar.
 (Drag starts, but when dropped no new tab is opened - although hyperlinks can
be dragged and dropped to the toolbar.)

Reproducible: Always

Steps to Reproduce:

Comment 1

[Jason Bassford]

-> XP Apps: Drag and Drop.  Sorry for SPAM due to my incorrect initial assignment.

Comment 2

[djk]

Part 1 of this report is bug 194802.

Comment 3

[Jason Bassford]

Thank you - modifying summary of that bug to include "drop" for better Bugzilla
queries.  And modifying summary here to focus on remaining problem.

Comment 4

[Jason Bassford]

Oops - wrong summary.  Sorry for the SPAM.

Comment 5

[Jason Bassford]

More investigation: Text drag and drop to the tab bar only fails if the text
dragged contains spaces.  (A simple word will work.)

Is this a bug or a "feature"?  Is there some mechanism in place determining
what's acceptable to be entered into the URL bar and rejecting anything that
doesn't qualify?

Comment 6

[Jason Bassford]

> Text drag and drop to the tab bar only fails if the text
> dragged contains spaces.

Can somebody please clarify if this is a bug or a feature?  I'd like to close
out this bug if it's doing what it should be doing.  Try dragging and dropping
two words separated by a space to the tab bar.  There is no X indicating it's
invalid, and it *looks* like something should happen, but it doesn't.  Surely, I
would think, it shouldn't just be ignored, but an error page should come up.

Comment 7

[Jason Bassford]

As of the 6/11-08 Win32 build, this is now "working" again.

I'm resolving this as WORKSFORME, rather than FIXED, since, from the lack of any
response as to it's bug or feature status, it's still unclear if it *should* be
working or not...  (Feel free to open a separate bug if you think that it was
actually a feature that it didn't work.)

Comment 8

[Jason Bassford]

.