Closed Bug 521808 Opened 15 years ago Closed 11 years ago

Restoring the default toolbar set results in 'a.initialize is not a function' being displayed in the error console.

Categories

(Firefox :: Search, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: u88484, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Australis:M?])

Restoring the default toolbar set results in 'a.initialize is not a function' being displayed in the error console.

STR:
1) Right-click on toolbar, select 'Customize...'
2) Click 'Restore Default Set'
3) Check error console and see the below error

Error: a.initialize is not a function
Source file: chrome://browser/content/search/search.xml
Line: 491
when using the 'sheet' method (default for mac) of customization, this is worse because the dialog then is frozen for dnd, requiring a close and reinit before customization can be done.  in non 'sheet' mode, the throw is transparent to the user.

looks like that binding constructor needs to check for one more parentNode higher..
OS: Windows Vista → All
Hardware: x86 → All
Component: Toolbars → Search
QA Contact: toolbars → search
I'm seeing this also in the new Australis customization code while running on Win7. Because of this bug being filed a while back I know that it isn't a new regression, but we may want to investigate it further to make sure that the side effects don't get worse.
Whiteboard: [Australis:M?]
This may have been fixed by the patch for bug 875042. Mike will check that this is fixed on Nightly.
Flags: needinfo?(mconley)
Yep, I can no longer reproduce this bug now that bug 875042 has landed.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mconley)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.