Description: This is a feature request. Would it be possible that when I click on the input field, the default entry is already highlighted, so that I can all I have to do is input a new entry? In the version I am using (6.1.0.3 (x64)), when I click on the input field, I have to highlight the default entry, then input a new entry. Steps to Reproduce: 1. Click on the input field Actual Results: 1. Default Entry is not highlighted. Cursor is on the first letter of the default entry. 2. I have to highlight all the default entry of the field. 3. Input a new entry. Expected Results: 1. Click on the input field 2. Default Entry is highlighted. 3. Immediately input a new entry. Reproducible: Always User Profile Reset: No Additional Info:
Thank you for reporting the bug. Could you please add a screenshot? It's not clea (t least for me) what you name "input field". I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 148071 [details] Current I have attached screenshots. I hope this makes it clear.
Created attachment 148072 [details] Feature request This is the screenshot of the feature request. Thanks.
Now it's clear to me. But it works as expected in Version: 6.1.4.2 (x64) Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Its still the same as 6.1.0.3 (x64) in my case. If I may add, this is not actually a bug, and the current set-up works fine. This is just a request for a minor enhancement.
I installed 6.1.4.2 (x64) but its still the same as 6.1.0.3 (x64) in my case. If I may add, this is not actually a bug, and the current set-up works fine. This is just a request for a minor enhancement.
*** This bug has been marked as a duplicate of bug 119303 ***
Thank you! Now resolved in 6.2 (Windows 7)