Closed Bug 53144 Opened 24 years ago Closed 24 years ago

click followed by drag becomes double click

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Windows 98
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: jruderman, Assigned: rods)

References

Details

Steps to reproduce:
1. Double-click on url bar to select everything
2. Wait at least two seconds
3. Click right after the http:// to prepare for selecting hostname
4. Quickly mousedown again

Result: selection starts from beginning
Expected: able to drag right to select hostname

I think that this is happening because Mozilla is interpreting a double-click 
in second mousedown.

This makes it difficult to select the hostname if the entire url starts out as 
selected.  I don't know whether Mozilla is going to end up doing this 
automatically when the url bar is clicked or not.
This is very simliar to an older bug, bug 39192.  In that bug, you drag first 
and then click.  In this bug, you click first and then drag.
cc pollmann, who recently fixed bug 51856.
IE and Nav do the same thing you're seeing on Windows, and Nav does the same
thing on FreeBSD (those are the only places I've tested).  I think that clicking
twice in a row in a text field is correctly flipping selection over to
"word-by-word" mode.  It just so happens that the text in the URL bar is
interpreted as all one word because there are no spaces.

Since this is a normal thing, marking this as INVALID.  If you disagree, please
reopen.  I've only done about five minutes of testing, so I could have
overlooked something!  :)
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
You're right, IE does this too.  Some smaller problems:

- Select word-by-word isn't quite working as advertised (bug 16203), so we end
up selecting from the beginning of the field to wherever the mouse pointer is.
This looks bad.

- The location bar shouldn't have select word-by-word or triple-click since it
usually doesn't have spaces.

- Mozilla seems to allow too much space between two clicks to consider the
second click a double-click.  This might just be my imagination, though.

None of this is a huge problem because Mozilla doesn't select the entire
location bar by default when you click on it.  (Bug 37587, invalid and mostfreq,
wanted to change this.)
Hi Jesse, thanks for looking at this more in-depth!

> - The location bar shouldn't have select word-by-word or triple-click since it
> usually doesn't have spaces.

This is the only point I disagree with.  Suppose the user wants to select the
entire URL bar with the mouse pointer at the far right edge of a URL.  IE and
Nav both allow this by double or triple clicking the URL then just typing in the
new URL.  If we turned off both word-by-word and triple-click for the URL bar
this would not be possible.  Our current implementation addresses the needs of
rewriting part of a URL (single click-drag) or an entire URL (double click) 

> - Mozilla seems to allow too much space between two clicks to consider the
> second click a double-click.  This might just be my imagination, though.

You're right, there is definitely a difference here.  I may have no rhythm, but
I did this test.  Begin tapping a rhythm out with your non-mousing hand.  Double
click at this pace.  Adjust rhythm until it is *just* slow enough to *not* count
as a double click an Windows native widgets (IE URL bar).  Now double click at
this same pace in Moz's URL bar.  It counts as a double click every time!  (even
slower than this will work, but twice as slow will not)

Bug 16203 comes into play a lot in terms of "feel" of the URL bar.  With any
other native widgets, when I single click + drag or "click and a half" as Eli
put it, the whole URL bar (or word) is selected, and the drag will not readjust
selection letter by letter.  Bug 16203 makes it harder to carelessly
double-click then edit the URL bar - you must be careful to hold the mouse
motionless while double-clicking.
>> - The location bar shouldn't have select word-by-word or triple-click since 
>> it usually doesn't have spaces.

> This is the only point I disagree with.  Suppose the user wants to select the
> entire URL bar with the mouse pointer at the far right edge of a URL.  

I was talking about word-by-word select as described in bug 16203 as opposed to 
double-click selection of a single word.  However, with your last comments, I 
now see that once bug 16203 is fixed it shouldn't matter whether the feature is 
enabled in the URL bar.

As for triple-click.. IE treats the third click in the location bar as a normal 
click, unselecting the selected text.  I wouldn't agrue against wontfix for 
this.

> Now double click at this same pace in Moz's URL bar.  It counts as a double 
> click every time!  

I have filed bug 53485 for this issue.
This is either a dup of or basically the Bug 39192
Updating QA Contact.
QA Contact: janc → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
QA contact updated
QA Contact: gerardok → madhur
Blocks: 91338
QA Contact: madhur → rakeshmishra
QA Contact: rakeshmishra → trix
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.