[faceted search] Error Console noise when gloda autocomplete suggests an email address from the address book

RESOLVED WORKSFORME

Status

Thunderbird
Search
RESOLVED WORKSFORME
9 years ago
9 years ago

People

(Reporter: Ilja Sekler, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090914 Firefox/3.7a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090914 Lightning/1.0pre Thunderbird/3.0b4pre

If the gloda autocomplete suggests an email address from the address book when typing into the global search input, the following error appears in the EC [1]:

Error: this.row.words is undefined
Source File: chrome://gloda/content/glodacomplete.xml
Line: 434

Typing a next word after a space throws an additional error [2]

Error: identity.pictureURL is not a function
Source File: chrome://gloda/content/glodacomplete.xml
Line: 553

At the first glance, these errors don't seem to break anything, just annoying.



Reproducible: Always

Steps to Reproduce:
1. Make sure that no search results tabs are open.
2. Type the first name of a person from your address book into the global search
3. Hit the space key and start typing the family name of this person

Actual Results:  
As soon as a gloda autocomplete dropdown shows an address book entry (an email address) during the step 2, the error [1] appears in the EC. The error [2] appears at step 3 as the first matching letter after the space is typed in.


Expected Results:  
No errors.


Thunderbird built from http://hg.mozilla.org/comm-central/rev/5c7fc4df7c25

My guess about the product and the component may be bloody wrong, as glodacomplete.xml lives in MailNews. Please move the bug to the correct place, if necessary and possible.
I think this got fixed at some point; I'm not seeing it with a current comm-1.9.1-ish build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.