Closed Bug 287096 Opened 20 years ago Closed 20 years ago

Find Toolbar Doesn't Work

Categories

(Toolkit :: Find Toolbar, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 274553

People

(Reporter: mozilla, Assigned: bugzilla)

References

()

Details

(Keywords: regression, testcase)

Attachments

(1 file)

20050321 trunk

The find toolbar does absolutely nothing while at this page.
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004002 (NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface]"  nsresult:
"0x80004002 (NS_NOINTERFACE)"  location: "JS frame ::
chrome://global/content/findBar.js :: getSelectionControllerForFindToolbar ::
line 209"  data: no]
This is a regression, works fine in 1.0.1
Keywords: regression
Flags: blocking-aviary1.1?
Can we get a regression window nailed down for this?
Flags: blocking-aviary1.1? → blocking-aviary1.1+
Attached file Testcase
This bug occurs when there is an iframe with display:none
Keywords: testcase
I've been seeing this problem for about a week, maybe more. Then again I only
started building Firefox again as of about a week or two ago, so it could have
been around a lot longer.

I've also been seeing the problem on *all* pages (so far as I've noticed). And
as the build I created about an hour ago the errors I'm getting are:

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/findBar.js :: toggleLinkFocus ::
line 407"  data: no]

Error: uncaught exception: [Exception... "Not enough arguments
[nsITypeAheadFind.findNext]"  nsresult: "0x80570001
(NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame ::
chrome://global/content/findBar.js :: findNext :: line 567"  data: no]
that last one seems different, and may be caused by an invalid list of
extensions being built (precisely: building with --enable-extensions=typeaheadfind)
I'm building with --enable-extensions=all
at the least, build with all,-typeaheadfind,-wallet, but that's what your bug
is, and not within the context of this bug.  If you further questions, please
ask via email/IRC.
Less a regression than an unnoticed aviary-landing bug, I'd say:

20041206: works
20041209: fails with "Error: Component returned failure code: 0x80004002
(NS_NOINTERFACE) [nsIInterfaceRequestor.getInterface] Source File: Line: 209"
and that error message persists until sometime between 20050106 (still that one)
and 20050111 (same as the current error message).
Find Toolbar didn't exist on trunk, and only landed then.  Unless I'm on crack,
blake didn't land one bit on trunk.

*** This bug has been marked as a duplicate of 274553 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.1+
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: