GNOME Bugzilla – Bug 714856
search highlighting is confusing
Last modified: 2016-06-19 08:52:00 UTC
---- Reported by chaz@yorba.org 2013-07-02 12:51:00 -0700 ---- Original Redmine bug id: 7191 Original URL: http://redmine.yorba.org/issues/7191 Searchable id: yorba-bug-7191 Original author: Charles Lindsay Original description: When you do a search and click on a resulting conversation, we highlight all tokens individually that match the tokens the database matched. Even saying it is confusing. For example, if you search for `johndoe@example.com`, we highlight all instances of `johndoe`, `example`, and `com`, even when those instances didn't contribute to a database match. This is confusing, misleading people that the wrong results are being returned from the database. We should highlight only the token sequence that caused the database to return a match to the query. Related issues: related to geary - 7183: underscore treated as punctuation by search (Need Information) related to geary - 7205: Special-case common search patterns that require punctuation (Fixed) ---- Additional Comments From geary-maint@gnome.bugs 2013-09-04 16:21:00 -0700 ---- ### History #### #1 Updated by Jim Nelson 5 months ago * **Target version** set to _0.4.0_ #### #2 Updated by Jim Nelson 3 months ago * **Target version** changed from _0.4.0_ to _0.5.0_ --- Bug imported by chaz@yorba.org 2013-11-21 23:12 UTC --- This bug was previously known as _bug_ 7191 at http://redmine.yorba.org/show_bug.cgi?id=7191 Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
*** Bug 738340 has been marked as a duplicate of this bug. ***
Marking as fixed since the fix for Bug 720361 included some code (ConversationViewer::add_literal_matches) to take care of this situation.