317898 - "find in page" doesn't actually find anything

Status: VERIFIED DUPLICATE of bug 292904

(Toolkit :: Find Toolbar, defect)

Description

[Brett Neumeier]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.9) Gecko/20050711 Firefox/1.0.5
Build Identifier: Firefox 1.5rc3

When I hit ctrl-F, the find toolbar opens as usual. When I type a search expression and hit return, nothing happens. The "find previous" and "find next" buttons also don't do anything.  If I click the highlight button, all instances of the search expression are highlighted, though.

I configured Firefox with:

  ./configure --prefix=/usr \
    --disable-accessibility \
    --disable-debug \
    --disable-installer \
    --disable-freetype2 \
    --disable-logging \
    --disable-mailnews \
    --disable-pedantic \
    --disable-tests \
    --disable-mailnews \
    --disable-ldap \
    --disable-profilesharing \
    --enable-application=browser \
    --enable-calendar \
    --enable-cpp-rtti \
    --enable-crypto \
    --enable-default-toolkit=gtk2 \
   --enable-extensions=all \
    --enable-libxul \
    --enable-optimize \
    --enable-single-profile \
    --enable-reorder \
    --enable-strip \
    --enable-xft \
    --enable-xinerama \
    --enable-xpctools \
    --enable-svg \
    --enable-system-cairo \
    --with-default-mozilla-five-home=/usr/lib/firefox-1.0.7 \
    --with-system-jpeg \
    --with-system-png \
    --with-system-zlib \
    --with-system-nspr \
    --with-user-appdir=.firefox

I'm going to attach the output from this configure command...

Reproducible: Always

Comment 1

[Brett Neumeier]

Attachment: stdout from the configure command

Comment 2

[Adam Guthrie]

What's the URL of the page this occurs on?

Comment 3

[Brett Neumeier]

This behavior occurs everywhere.

My suspicion is that something in Firefox didn't get built properly, either because of a bad configure switch or because of something wrong on my system. But everything builds cleanly, so I don't know what it would be.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

See bug 292904 comment 3. Using |--enable-extensions=all,-typeaheadfind| should fix it.

*** This bug has been marked as a duplicate of 292904 ***