445727 - Web form autocomplete throws uncaught exception when losing focus without selection

Status: RESOLVED DUPLICATE of bug 428602

(Toolkit :: Autocomplete, defect)

Description

[Eemeli Aro [:eemeli]]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061017 Firefox/3.0
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008061017 Firefox/3.0

When a web form textbox autocomplete dropdown list is closed with a highlighted item that isn't selected, the following error results:

Error: uncaught exception: [Exception... "Cannot modify properties of a WrappedNative"  nsresult: "0x80570034 (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)"  location: "JS frame :: chrome://global/content/bindings/autocomplete.xml :: onxblpopuphiding :: line 834"  data: no]


Reproducible: Always

Steps to Reproduce:
1. Open and clear the error console
2. Go to a page (eg. google.com) with an input text box that you've used before
3. Press the down arrow or enter some text to show the autocomplete dropdown list
4. Hover with the mouse or select with arrow keys any of the options
5. Click anywhere else on the page, closing the autocomplete but not changing the textbox value
6. Observe the error console



Tested with Firefox 3.0 on Ubuntu Hardy and Windows XP; verified as not happening with Firefox 2.0.0.15 on Windows XP.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Confirmed on Windows XP. On 6 March 2008 I saw this error for the first time. It changed from:

Error: this.mInput._focus is not a function
Source File: chrome://global/content/bindings/autocomplete.xml
Line: 831

to:

Error: uncaught exception: [Exception... "Cannot modify properties of a WrappedNative"  nsresult: "0x80570034 (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)"  location: "JS frame :: chrome://global/content/bindings/autocomplete.xml :: onxblpopuphiding :: line 828"  data: no]

Regression range second error (what this bug is about) is:
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1204836060&maxdate=1204859519
Could be caused by Bug 419725.

The first error was caused by Bug 407359.