Open Bug 892851 Opened 11 years ago Updated 2 years ago

findbar binding's constructor relies on accessibility.typeaheadfind prefs not defined in toolkit

Categories

(Core :: XUL, defect)

x86_64
Windows 7
defect

Tracking

()

People

(Reporter: WeirdAl, Unassigned)

References

()

Details

(Keywords: access)

In my XULRunner app, I loaded the Error Console (chrome://global/content/console.xul) as an iframe.

Timestamp: 7/11/2013 9:39:20 PM
Error: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]
Source File: chrome://global/content/bindings/findbar.xml
Line: 363

The offending line is prefsvc.getIntPref("accessibility.typeaheadfind.flashBar");

The URL field shows a list of references to accessibility.typeaheadfind in the source code.  Unfortunately, the preference is not defined for the whole toolkit; the findbar widget blindly assumes the preference exists and is an integer.

The findbar widget needs some reasonable defaults for when it comes from a different XULRunner application.
Ping for this:

Timestamp: 2014/11/19 15:09:12
Error: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]
Source File: chrome://global/content/bindings/findbar.xml
Line: 323
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.