It looks like 'search-result-count' isn't emitted anymore, which makes it problematic for knowing when to enable the find next/prev buttons. I would expect to: - disable the next/prev buttons - launch highlight_all('my-search-string'); - wait for search-result-count > 0 (or a "search-found" signal) to enable the next/prev buttons
Dear Reporter, 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.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170830
The bug is as much there as it was when I filed it, as far as I know.
I do not see any mean to test this bug report. Please, could you describe a step by step procedure to reproduce this problem? Status set to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #4) > I do not see any mean to test this bug report. Write a program that uses the LOKDocView, and connect to the search-result-count. This is all in comment 0.
Hi Kendy, Do you know anyone who could investigate this issue ?
Had this issue when we were printing documents for our site, https://nashvillehoodcleaning.net, good thing I encountered your post here.
Hello Bastien, is this issue still reproducible in a master build ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
(In reply to Xisco Faulí from comment #8) > Hello Bastien, > is this issue still reproducible in a master build ? > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the master build I don't think that me testing for bugs that nobody intends on fixing is a good use of my time.
[Automated Action] NeedInfo-To-Unconfirmed
Miklos: looks like you added LOKDocView::search-result-count in 22d342a82f225381057b5b8b941be8583de87a63. Kendy made a pretty important typo fix in c0f37892a24b202c0a28836ed1046c90c7631e03 Bastien's report was made only two months after the implementation. A note to Bastien: if you had included an example program, a tester with no experience with LOKit might have bisected the issue and essentially handed it to developers on a silver platter.
(In reply to Buovjaga from comment #11) > Miklos: looks like you added LOKDocView::search-result-count in > 22d342a82f225381057b5b8b941be8583de87a63. > > Kendy made a pretty important typo fix in > c0f37892a24b202c0a28836ed1046c90c7631e03 > > Bastien's report was made only two months after the implementation. > > A note to Bastien: if you had included an example program, a tester with no > experience with LOKit might have bisected the issue and essentially handed > it to developers on a silver platter. The person working on LOKit was the same person working on the gnome-documents backend, so they would have known how to test this. I'm not sure that advice on how to report a good bug 8 years after it was filed is as useful as you think it is. In any case, gnome-documents doesn't exist anymore, so feel free to close this.
Dear Bastien Nocera, 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