Page MenuHomePhabricator

Drag and drop a text fragment to top-right search box adds it to the placeholder
Closed, ResolvedPublic

Description

Affects Firefox 38.

How to reproduce

  • Select some text.
  • Drag and drop it to the top right search box

Expected behavior

The actual value of the form is the text moved there

Actual behavior

The text is appended to the placeholder.

When we click on the input box, it's discarded.

Event Timeline

dereckson raised the priority of this task from to Needs Triage.
dereckson updated the task description. (Show Details)
dereckson added projects: Design, Javelin.
dereckson updated the task description. (Show Details)
dereckson added a subscriber: dereckson.

I can't reproduce this in Safari 8.0.4 on OSX.

chad added a subscriber: chad.Mar 30 2015, 3:24 PM

How do you "Drag and drop text"? I've no idea what that means, at least trying it in Chrome and Firefox, it's not possible on any site?

Here's how I do it in Safari:

  • Select any text.
  • Click and hold the selected text without moving your mouse. On OSX, you have to hold this click for about a second or a second and a half for the OS to recognize it as "drag" instead of "select".
  • After a second or two, drag it around.

I can reproduce the report only in Firefox; Chrome and Safari work fine for me.

chad added a comment.Mar 30 2015, 3:31 PM

In a browser or text from somewhere else, I can't even get this to trigger. I've honestly never heard of this in 20 years of building web pages.

chad added a comment.Mar 30 2015, 3:32 PM

Haha, ok, after like 10 tries I got it. Takes longer for me to use that mechanic than simple copy/paste.

Yeah, I'm pretty sure I've only ever used this by accident.

dereckson updated the task description. (Show Details)Mar 30 2015, 3:46 PM
chad renamed this task from Drag and drop a text fragment to top-right search box adds it to the placeholder. to Drag and drop a text fragment to top-right search box adds it to the placeholder.Mar 30 2015, 3:49 PM

The issue doesn't appear in the current code base with Firefox 73. That's not unexpected, as the UI has been tweaked several times between 2015 and now.

So we can mark this resolved I guess (I'm not sure a git bisect to identify the solving commit is useful for such a trivial thing)?

epriestley closed this task as Resolved.Wed, Mar 11, 3:38 PM
epriestley claimed this task.