Description: In Writer, if the Navigator is first displayed, the cursor focus is in the Navigator panel instead of in the text area. As a result, in a new document, you have to reposition the cursor before you can start writing. Steps to Reproduce: 1.a. With a document on screen, hit F5. b. Alternatively, just start Writer after having it closed down with the Navigator displayed. c. Alternatively, with Writer open and Navigator displayed, hit CTL-N. 2. Hit any key. Actual Results: Keystrokes apply to the Navigator panel. (Not even CTRL-W works!) Expected Results: At least in cases #1b and #1c above, the cursor must stay in the text area. Reproducible: Always User Profile Reset: No Additional Info: a) One might argue whether the current behavior makes sense in case #1a. However, in cases #1b and #c, it is a nuisance; the cursor must be in the text area. b) The behavior is multiply inconsistent. Behavior #1b and #c does not happen if you open an existent document; then the cursor is in the text area (which is, of course, good). Nor does the counterpart of behavior #1a happen with the Styles list: if you open it (e.g. by hitting F11), the cursor remains in the text area (which, again, is good). Suggestion: To keep consistency, always keep the cursor in the text area unless the user moves it to the Navigator (just as it is now with the Styles list). User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
(In reply to Christian Lehmann from comment #0) > Expected Results: > At least in cases #1b and #1c above, the cursor must stay in the text area. That is the result I recieve with Version: 6.0.4.2 (x64) Build-ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
It definitely does not happen with build Build-ID: 1:6.0.4~rc2-0ubuntu0.16.04.1. The cursor in the Navigator is replicable _always_.
I reproduce the case #1c. I do not reproduce the case #1b with LO 6.0.4 and 6.1.0.0.beta1+ Another problematic case: 1/ configure LO to use the sidebar 2/ open an existing text document, click somewhere in the text to see the cursor if it is not visible 3/ click on the icon of a panel of the sidebar => the cursor is not visible anymore in the text document and starting writing does nothing. As the sidebar may be used as informative panel (document structure, document formatting, etc.) opening a sidebar panel should not disable the cursor in the text area. Setting status as NEW. Best regards. JBF
To confirm case #1.b above, take the following steps: 1) Load any document into Writer. 2) Display the Navigator, e.g. by hitting F5. 3) Close the document and Writer. 4) Start Writer again. It will show you a white page and the Navigator panel, and the cursor will be in the panel instead of in the text area. If you cannot reproduce this with LO 6.0.4.2 on Ubuntu 16.04, some magic must be at work. I can reproduce _your_ observation. However, one may discuss what is useful behavior in this case. If I click on an item in the Navigator bar, I transfer the graphical cursor into that area. One may argue that I then want it to be there. This may require further analysis. Best, Christian
(In reply to Christian Lehmann from comment #4) > To confirm case #1.b above, take the following steps: > > 1) Load any document into Writer. > 2) Display the Navigator, e.g. by hitting F5. > 3) Close the document and Writer. > 4) Start Writer again. I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: 3bd8759f5ed0393b2cc5560cab1b5d4052bd9728 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded Could you please paste the info from Help - about LibreOffice ?
Created attachment 142674 [details] my LO version Here you are, Christian
Dear Christian Lehmann, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Not reproducible anymore for me with Version: 7.3.6.0.0+ / LibreOffice Community Build ID: 97c759c09fce906d44fba98d325e3729c4a96665 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu_20.04_x86-64 Calc: threaded Best regards. JBF
Not reproducible anymore in version 7.3. Some magic must have remedied it.