After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778033 - Find in conversation does not work anymore
Find in conversation does not work anymore
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: client
master
Other Linux
: High normal
: 0.12.0
Assigned To: Geary Maintainers
Geary Maintainers
wk2-fallout
Depends on:
Blocks:
 
 
Reported: 2017-02-01 14:25 UTC by Federico Bruni
Modified: 2017-02-28 15:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Federico Bruni 2017-02-01 14:25:19 UTC
After the merge in master of WK2 branch, find in conversation does not work anymore.

It does not unfold the message containing the keyword, it does not highlight the instances of found keyword and no way to go to the next item with Ctrl+G shortcut.
Comment 1 Michael Gratton 2017-02-01 14:37:40 UTC
Hmm, this seems to work intermittently for me:

 - Messages with matches in the body aren't unfolded, but they are still highlighted
 - Message with matches in headers (from, subject, etc) are unfolded

Does that match what you are seeing or are you getting something else?
Comment 2 Federico Bruni 2017-02-01 14:57:02 UTC
You are right. I didn't test it carefully.

After few more tests, I believe that it finds matches only in the current active message. It does not look in all the messages of a conversation.

For me only messages with matches in from are unfolded (while messages with matches in subject are not unfolded).
Comment 3 Michael Gratton 2017-02-23 00:42:30 UTC
Fix for general search issues just pushed to master as commit ae33745 and subject not being highlighted as commit 928189f.

There's an issue highlighting (and hence unfolding) more than one search term die to WK2 API changes, so this issue still exists for account searches (not in-conversation find) with more than one term, just created a bug for that however: Bug 779105.

Federico, aside from the above does this take care of the issues you're seeing?
Comment 4 Michael Gratton 2017-02-28 10:46:43 UTC
I'm pretty happy with how this is working at the moment, so closing this. If you spot any other issues, please open a new bug.
Comment 5 Federico Bruni 2017-02-28 15:21:04 UTC
Yes, it works fine now!
Except the CTRL+G shortcut to go to the next found item. Is it already covered by another bug report?
Comment 6 Michael Gratton 2017-02-28 15:35:43 UTC
Cool, glad to hear it! Re-enabling Next/Prev is Bug 778021.