Description: When a find operation switches from slides to notes, or vice versa, the found text is selected for deletion or replacement. This is probably related to bug 123665. Steps to Reproduce: I first created a test presentation (attached) with the following three slides: Slide Title Slide Notes Slide 1 First page of notes This is the first slide of three Slide 2 Second page of notes This is the second slide of three Slide 3 Third page of notes This is the third slide of three 1. In the slide pane, click on the first slide. Click on the Normal tab to display the slide. 2. Choose Edit / Find, or press Ctrl-F. In the search box, type "slide" (without the quotes) and click the "find next" button (the large down-arrow in the Find toolbar at the bottom of the screen). The word "Slide" is highlighted. This is correct. 3. Continue clicking the "find next" button until the notes view of slide 1 is displayed. (Nothing is highlighted -- see 123665.) 4. Click the "find next" button again. "Slide" is highlighted, and there is a blinking vertical-bar cursor after the word. Pressing Enter or any other key at this point causes the word "slide" to be replaced by whatever is typed. Actual Results: See above. Behavior is inconsistent: on the slides, the highlighted text will not be deleted on pressing Enter. (In fact, Enter acts the same as "find next.") On the notes, the highlighted text, with the blinking cursor, will be deleted by Enter. This is different from text searches in Writer, in which Enter and "find next" work identically and the found text never shows a cursor. Note that a similar thing happens if the search is started when Notes is displayed: when the search switches to Normal slides, the next highlighted result includes a cursor. Expected Results: I expected the text found by the search to be selected, but not to be deleted if I press Enter. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.1.5.2 (x64) Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group threaded
Created attachment 149547 [details] Test presentation, as described.
Thank you for reporting the bug.I can reproduce the bug. Version: 6.3.0.0.alpha0+ Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
It used to be worse: in 4.3.0 and older Enter replaces the text even in Slide view. Also repro on Linux. Potentially an accessibility issue, so keeping severity as normal. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: 558956dc811a1f0f07411e348f7081a467bbc3b5 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 4 April 2019
Dear David F Smith, 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
Retested this bug, which is probably related to bug 123665. The behavior is exactly the same as in my original report. Version: 7.0.5.2 (x64) Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Dear David F Smith, 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
I have retested under 7.4.6.2, and now the results are exactly what I expect. I have changed the status to RESOLVED-WORKSFORME. Thank you. Version: 7.4.6.2 (x64) / LibreOffice Community Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded