Closed
Bug 183112
Opened 22 years ago
Closed 17 years ago
click and hold cancels (aborts) selection if no mouse movement
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: michael.norris, Assigned: mikepinkerton)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021201 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021201 Chimera/0.6+
Chimera does not respect one of the normal Mac OS text-editing protocols in its
textfields. Normal protocol is that if you double-click a word to select the
word, and while holding the second click, drag to the left, the word should
remain selected. In Chimera 0.6, the word becomes *deselected*. Furthermore, if
you hold down the second click and wait for a second or so without moving the
mouse, you are no longer able to drag left *or* right. Do
Reproducible: Always
Steps to Reproduce:
1. Enter some text in an on-screen textfield (e.g. Google.com)
2. Double-click one of the words
3. While holding down the second click, drag to the left.
4. Repeat, but holding down for two seconds without moving the mouse.
5. Try this in TextEdit and notice the difference.
Expected Results:
Textfields should behave like normal NSTextViews...
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•22 years ago
|
||
This is a long-standing Mozilla bug.
Summary: Text selection bug in textfields: double-clicking a word and dragging left → Double-click drag text selection doesn't use OS standards
Comment 2•22 years ago
|
||
Sounds like another vote for native text widgets.
Comment 3•22 years ago
|
||
*** Bug 186742 has been marked as a duplicate of this bug. ***
Comment 4•22 years ago
|
||
Comment 5•21 years ago
|
||
resummarizing to deal with remaining issue (which may be a duplicate)
Summary: Double-click drag text selection doesn't use OS standards → click and hold aborts selection if no mouse movement
*** Bug 214938 has been marked as a duplicate of this bug. ***
Is there any reason this isn't in Core:Selection (other than the fact it's even more broken in Fx because they have click-hold context menus)?
My question in the previous comment still stands; so far, it hasn't gotten more attention (fixed) staying here ;)
Blocks: 330968
Severity: normal → minor
QA Contact: winnie → general
Summary: click and hold aborts selection if no mouse movement → click and hold cancels (aborts) selection if no mouse movement
Comment 12•17 years ago
|
||
The second part is gone in trunk, so closing WFM.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•