When clicking in a combobox with a single mouse click or tab key, the content should be selected/marked instead of the necessity of using a double-click with the mouse. I know this is a different behavior than in the content view (words are only selected/marked after double-clicking on it, paragraphs with tiple-clicking). But the UX team should discuss to change the default behavior because its more likely that the user wants to change the whole content of the combobox than to only add a character to the existing combobox content. For example, when clicking into the font size combobox in the formatting toolbar, the displayed number should be marked so that the user only has to type a new number and enter. Now the user has to click into the combobox, has to mark or delete the number by hand, must type a new number and has to type enter. When clicking a second time, the marking should be changed to only a blinking cursor in the clicked position in the combobox (as a single click acts today).
Created attachment 136696 [details] Screenshot of current behavior when clicking in a combobox and what's demanded
Just for information: The Find Text combobox in the Find toolbar works exactly as I suggest it for other comboboxes (font name, font size, set style).
(In reply to Thomas Lendo from comment #0) > When clicking in a combobox with a single mouse click or tab key, the > content should be selected/marked instead of the necessity of using a > double-click with the mouse. As a combobox is a text field, like a textbox, clicking in it with a mouse shouldnt select all the text. Using tab should select the text, as it does so in dialogs and spinboxes in the sidebar, though strangely it doesnt happen to spinboxes in the toolbar.
Consistent behavior is paramount and I support Thomas' idea. In text fields you likely do not want to change all text (except URLs for instance, type ctrl+L in your browser) but in case of numeric inputs the primary workflow is to enter a complete new value (of course subsequently to thumb/click/wheel input).
+1
(In reply to Heiko Tietze from comment #4) > Consistent behavior is paramount Totally agree its important and LibreOffice should behave like other OS apps in what to do. So Heiko, what does KDE HIG say about single click in a combobox? In MS Office and WPS, single click in combobox and spinbox in ribbon selects, while in a dialog it doesnt.
(In reply to Yousuf Philips (jay) from comment #6) > what does KDE HIG say about single click in a combobox? That's not defined in KDE HIG. Kate, as a KDE app, selects all content on tab but none on click, which feels more familiar to me.
No need for further input from UX. Please select the content of editable fields on enter (tab or click).
Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Paragraph combobox still not changed. Version: 6.3.2.2 (x64) Build-ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win
Dear Thomas Lendo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro with this version of LibreOffice: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9a02f4ed071f15908624fb1cafcf6dbb72b00a1b CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: threaded