Bug 149254 - Make the selection behavior when double-clicking a word a user preference.
Summary: Make the selection behavior when double-clicking a word a user preference.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Selection
  Show dependency treegraph
 
Reported: 2022-05-24 05:28 UTC by Chris
Modified: 2022-06-16 14:08 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Double-Click Behavior Writer (36.27 KB, image/png)
2022-05-25 20:38 UTC, Chris
Details
Double-Click Behavior of MS Word (67.82 KB, image/png)
2022-05-25 20:40 UTC, Chris
Details
Double-Click Behavior Google Docs (22.82 KB, image/png)
2022-05-25 20:45 UTC, Chris
Details
Another example in Google Docs (156.86 KB, image/png)
2022-05-25 20:48 UTC, Rafael Lima
Details
Double-Click Behavior Bugzilla (7.94 KB, image/png)
2022-05-25 20:52 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2022-05-24 05:28:25 UTC
I would like to see the behavor when double-clicking a word be user-modifiable preference.  Most WYSIWIG editors I use, including the one I'm using to create this report, select a group of consecutive letters plus trailing whitespace up to the punctuation or the next letter.  Writer selects only the word.  This is not necessarily /wrong/ behavior, however it is contrary to what my muscle memory expects.  The behavior is especially bothersome when editing a document as I tend to write a lot and then delete words either as a group, or one at a time.  To delete a word I have to hit the delete key twice, once for the word, once for the space.  

This is an admittedly minor point, but it can be irritating when I really want to focus on what I'm doing rather than the technology.

Thanks!

Chris
Comment 1 Rafael Lima 2022-05-24 15:57:38 UTC
Hi Chris, thanks for reporting this issue.

However, I do not clearly understand your request because the current double-click effect we have in Writer is the same in MS Word, Google Docs, as well as the text input here in Bugzilla.

For instance, when I double-click a word, the entire word is selected. I have never had a different result in any other application. What WYSIWYG editors do you use? In which OS?

In Writer, you can use multiple clicks to select a word (double-click), sentence (triple-click), or paragraph (quadruple-click).
Comment 2 Chris 2022-05-25 20:38:08 UTC
Created attachment 180382 [details]
Double-Click Behavior Writer

This screenshot reflects the behavior of Writer in my experience -- it selects only a string of text between whitespaces.  Hitting Delete at this point will leave two consecutive spaces in the work.
Comment 3 Chris 2022-05-25 20:40:25 UTC
Created attachment 180384 [details]
Double-Click Behavior of MS Word

Word selects the word, plus any trailing spaces.  The fact that it picks up those consecutive spaces may also create problems, but that is a topic for another discussion.
Comment 4 Chris 2022-05-25 20:45:00 UTC
Created attachment 180385 [details]
Double-Click Behavior Google Docs

Google Docs emulates the behavior of MS Word (and this editor) by selecting the text string plus the trailing space.
Comment 5 Rafael Lima 2022-05-25 20:48:35 UTC
Created attachment 180386 [details]
Another example in Google Docs

This is a bit weird. See in my screenshot that double-clicking a word in Google Docs only selects the word (not the trailing spaces).

What operating system are you using? What Web browser do you use with Google Docs?
Comment 6 Chris 2022-05-25 20:52:07 UTC
Created attachment 180387 [details]
Double-Click Behavior Bugzilla

This selection shows several spaces beyond a double-clicked word being selected.
Comment 7 Rafael Lima 2022-05-25 20:57:06 UTC
As a follow-up to Comment 5, when I double-click a word in Google Docs, indeed just the word gets selected.

However, if I press delete only one space is left between both words, which is very handy and prevents the user from making the mistake of leaving two consecutive blank spaces.

LibreOffice Writer would have left two consecutive blank spaces in this case, which is indeed not a great experience. I myself have made a few mistakes in documents due to this behavior.

IMO when we select a word and delete it, only one blank space should be left, as MS Word and Google Docs do. Let's hear the UX team's opinion on this.
Comment 8 Chris 2022-05-25 21:02:29 UTC
I see from your examples that perhaps there is a regional component to this.  For me that is all the more reason to have the behavior be user-selectable.  

Thank you for taking an interest.  I hope we can find a way to make this improvement to Writer!
Comment 9 Chris 2022-05-25 21:04:08 UTC
(In reply to Rafael Lima from comment #5)
> Created attachment 180386 [details]
> Another example in Google Docs
> 
> This is a bit weird. See in my screenshot that double-clicking a word in
> Google Docs only selects the word (not the trailing spaces).
> 
> What operating system are you using? What Web browser do you use with Google
> Docs?

I'm in Windows 10 and using Brave browser.  The behavior is consistent from one browser to another for me.  As noted, there may be a regional component to this.
Comment 10 Heiko Tietze 2022-05-31 11:32:04 UTC
We should not add magically do something and rather select the exact characters. This means "Hello <brave >new world" with brackets for the envisioned selection. Works for delete but not if you replace the word - you'd have to add the trailing space in this case again.
And btw, trailing or leading white space? Probably depending on whether at the beginning of the sentence or at the end.

I vaguely remember a similar ticket, but bug 100189 is different and I cannot find anything better.
Comment 11 Chris 2022-06-01 23:50:35 UTC
Heiko Tietze, you are correct of course.  I'm looking for a consistent experience that I can adjust to my needs.  If I could adjust it, double-clicking a word would act like MS-Word which selects the word plus the trailing space.  A delete or a backspace removes the word, plus the trailing space.  Overtyping preserves the space, or more correctly, replaces the trailing space.  There may be some other options, but this is something that I've grown used to, and I'd prefer not to have to re-learn how to use the word processor as I'm trying to write or edit a document.

Thanks for your consideration.  I don't want to add to bloat, and I really don't want to complicate configuration menus, but this one feature would be really helpful as I edit my writing.

Chris
Comment 12 Heiko Tietze 2022-06-09 06:16:46 UTC
We discussed the topic in the design meeting.

Some good arguments support this request, first of all convenience (select and delete/over-type without need to adjust spaces) and consistency (most competitors do so). But in fact we do the expected behavior when the selection is done by keyboard (shift+ctrl+right - or left in case of RTL). And we should implement the same for mouse interactions.


Bug 149308 requests the opposite to not include trailing spaces (NAB/WF IMO)

Bug 82735, bug 136053 discuss whether deleting a word should automatically include the trailing space (resolved WF since we delete the selection - and the selection should include the white-space)

Bug 129426 is about collapsing the selection
Comment 13 Heiko Tietze 2022-06-09 06:19:34 UTC
Addendum: We recommend adding trailing spaces to the selection should _not_ made optional.
Comment 14 Chris 2022-06-13 19:24:26 UTC
(In reply to Heiko Tietze from comment #13)
> Addendum: We recommend adding trailing spaces to the selection should _not_
> made optional.

I don't disagree -- making it optional is pretty granular and might generate more heat than light.  At the very least double-clicking a word and then deleting it should not leave an "extra" space and instead leave the words on either side with a single space between them.

Thanks you for your interest.  I look forward to seeing my little contribution in an upcoming iteration of LibreOffice!

Regards,

Chris