Closed
Bug 88228
Opened 24 years ago
Closed 19 years ago
Double-click on a word shouldn't select the space afterwards when in read-only mode
Categories
(Core :: DOM: Selection, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: adamlock, Unassigned)
References
Details
When I double-click on a word in some browser or email content it should not
select the space following the word. In circumstances where the text is
read-only the user will more often than not just want to select the word and
not include the space.
The reverse is true for editable areas such as text fields and the composer,
where selecting the space is useful because makes it easier to do text cut and
paste operations.
The other bug looks too all-encompassing. It might be better to make
dependency between the other one and this one which is describing a very
specific issue.
*** This bug has been marked as a duplicate of 16352 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Duplicate was turned into bug 98546, which is fixed, but this isn't.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Assignee: mjudge → selection
Status: REOPENED → NEW
QA Contact: tpreston
Comment 7•19 years ago
|
||
*** Bug 317344 has been marked as a duplicate of this bug. ***
Comment 8•19 years ago
|
||
Quoting from
[http://www.mozilla.org/access/keyboard/proposal#II._Keyboard_Navigation_in_a_Block_of]:
"<ctrl+right> is more complicated - its behavior depends on a preferences
setting layout.word_select.eat_space_to_next_word.
It defaults to true on Windows, but false on Linux/Solaris/Mac."
While I must admit this is weird, this is consistent with how Windows works,
and is therefore a default setting in Firefox. If you wish to change this, open
about:config, search for layout.word_select.eat_space_to_next_word, and change
its value to false. This will stop the problem for you.
Marking INVALID, as this is not a bug but a "feature" thanks to Windows. :)
Status: NEW → RESOLVED
Closed: 24 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•