Created attachment 116731 [details] Shows how the focus is lost from the current slide in the "Slides" pane In the "Notes" view, the current slide is highlighted in the "Slides" pane. But once I click inside the "Notes" pane, this highlight vanishes. Thus I lose sight of where I am in the presentation. Even if I switch to the "Slides" pane, the highlight is not restored. There is a workaround, though: While editing in the "Notes" pane, I have to press PgUp or PgDown. Now the "slides" pane starts showing the highlight again. But at this stage, the focus is neither in the "Slides" pane nor in the "Notes" pane! * If the focus is in "Slides" pane, I should be able to switch between slides by pressing the Up/Down arrows, not by pressing PgUp and PgDown! * If the focus is in the "Notes" pane, I should be able to move around the pane and also edit the text. But I am not able to do either of the above! I have to explicitly go to the "Slides" pane or the "Notes" pane by clicking there. Till that time, I am in neither of the panes. Desired: 1. Even when I am working in the "Notes" pane, the current slide should be marked with a dotted line, to signify that this is the current slide, but my focus is in a different pane. 2.If I am in the "Notes" pane of a slide, and if I press PgUp or PgDown, Impress should take me directly to the notes section of the previous/next slide. That way, I can remain in the "Notes" mode, and edit the notes for all slides in one go.
Reproduced. My first try didn't lose the highlight, but all my other tries did, so watch out, reproducers. Win 7 Pro 64-bit, Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Locale: fi_FI Version: 5.1.0.0.alpha1+ (x64) Build ID: a51ac4d2bb8c4f1ea1d4ea7569863e2fb6535b02 TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-06-22_21:37:53 Locale: fi-FI (fi_FI) Versio: 5.0.0.1 (x64) Käännöksen ID: 9a0b23dd0ab9652e0965484934309f2d49a7758e Maa-asetus: fi-FI (fi_FI)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
still repro in Version: 6.3.0.0.alpha0+ Build ID: 4aa8a6ab08b755e3d82860e8dbc294f854336477 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-03-14_17:51:01 Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US Calc: threaded
Dear narayanaras, 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
I confirm this is still present in the current (7.1.5) version It's been fixed quite recently in the main editor "Normal" mode, but not the "Notes" mode. 1. Go into the Notes view, with the Slides pane visible. 2. Select a slide, from the left, and then click into the slide and start typing. 3. In the left, you can no longer see which slide you're working on. i.e the UI has correctly given mouse-focus to the notes field, but has incorrectly stopped highlighting the background of the active slide.
Also repro with Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded and also using LibreOffice 3.4.0 OOO340m1 (Build:11) but not using LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
(In reply to RichardNeill from comment #5) > It's been fixed quite recently in the main editor "Normal" mode, but not the > "Notes" mode. This looked promising, since knowing what have fixed a similar case could radically simplify fixing this one. So I tested 5.0.0.5, 6.0.0.3, and 7.0.0.3 on Windows to see if standard mode suffered a similar problem in those. But in all those I couldn't see that problem in normal mode. If you know a specific version that suffered from the similar problem in another mode, but had fixed in 7.1, please mention the version here. Thanks!
Confirming with Version: 7.4.1.2 / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Mac OS X 12.6; UI render: default; VCL: osx Locale: de-DE (en_DE.UTF-8); UI: en-US Calc: threaded
*** Bug 121847 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #8) > Confirming with After switching to the Notes view the currently active slide remains in focus. But after another slide is selected the highlighting disappears after clicking somewhere.
*** Bug 152620 has been marked as a duplicate of this bug. ***
*** Bug 125760 has been marked as a duplicate of this bug. ***