Created attachment 82598 [details] Allows to easily demonstrate the bug. How to reproduce: * Open the attached document. * Search for "Zitates". * Notice that he occurrence within the comment is never reached.
Not reproducible on LO 3.6.6.2 (Ubuntu 12.04 32bit). If you meant white colored words, in my opinion white colored word won't occured but found while do searching.
OK, so search for "Quelle". There should be 2 occurrences in the document. One as white text, and one within the comment. However when using the search, you'll find only the first occurrence. Can you confirm that?
Ok I can confirm that with LO 4.0.4.2 (Win7 32bit) But I don't know whether it's a bug, because we can do that using 'Find & Replace' dialog box as Joel mentioned in Bug 62518: https://bugs.freedesktop.org/show_bug.cgi?id=62158#c1
> Replace' dialog box as Joel mentioned in Bug 62518: Ups..slipped when typing. I meant Bug 62158
Comment on attachment 82598 [details] Allows to easily demonstrate the bug. fixed mime type, as not recognized correctly :S
Confirmed with LO 4.1.0.3, OS X 10.8.4. Imo a valid enhancement request. If I search a document, I want everything (and that includes comments) searched. Imo that would be appropriate default behavior. It is not thus setting to NEW.
** 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 (4.4.1 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Confirmed. Win 7 Pro 64-bit Version: 5.0.0.0.alpha0+ (x64) Build ID: 211c12b9c64facd1c12f637a5229bd6a6feb032a TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-18_01:51:17 Locale: 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
Confirmed with LO 5.2.2.2. I agree with Comment 6: "If I search a document, I want everything (and that includes comments) searched. Imo that would be appropriate default behavior." This is especially appropriate in case of a text occurring only in a comment in an otherwise long document: the document is successfully found by Spotlight as containing the text, and then LO does not find the text itself!
I don't understand why this should be a bug, because writer gives you the possibility to search within comments (find & replace => more optins => comments). And I think it is important that you can choose searching within the comments or not. So my proposal is to close this bug as WORKSFORME.
It could be a useful to search only within comments. Bug 96474 is about this enhancement.
(In reply to Dieter Praas from comment #11) > I don't understand why this should be a bug, because writer gives you the > possibility to search within comments (find & replace => more optins => > comments). And I think it is important that you can choose searching within > the comments or not. So my proposal is to close this bug as WORKSFORME. Oh, you're right, man..
*** Bug 160089 has been marked as a duplicate of this bug. ***