Closed Bug 274193 Opened 20 years ago Closed 20 years ago

Find next/previous (ctrl+g) doesn't work

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: bumbyn, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041211 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041211 Firefox/1.0

Find next/previous doesn't work with either typeahead or the find-box. I can
highligt the search pattern and find first, but find next doesn't do anything.

Reproducible: Always
Steps to Reproduce:
1. Start firefox
2. Go to a page with some text
3. typeaheadfind (/) for a word/letter that occurs more then once on the page
4. press ctrl+g to find next

Actual Results:  
nothing

Expected Results:  
moved selection to next occurens of the word I searched for

I've tried with both root and normal user. Also tried recompiling. Older (<1.0)
versions have not had this problem.

I compiled firefox with:
export MOZ_PHOENIX=1
export BUILD_OFFICIAL=1
export MOZ_CALENDAR=0
export MOZ_ENABLE_XFT=1
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/build
mk_add_options MOZ_PHOENIX=1
mk_add_options BUILD_OFFICIAL=1
ac_add_options --prefix=/opt/firefox-0.9.3
ac_add_options --with-user-appdir=.firefox
ac_add_options --with-system-zlib
ac_add_options --with-system-jpeg
ac_add_options --with-system-png
ac_add_options --with-pthreads
ac_add_options --without-system-nspr
ac_add_options
-enable-extensions=cookie,xml,-rpc,xmlextras,pref,transformiix,universalchardet,typeaheadfind,webservices,inspector,g
nomevfs,negotiateauth,-irc,-venkman,-content-packs,-help
ac_add_options --enable-default-toolkit=gtk2
ac_add_options --enable-toolkit-gtk2
ac_add_options --enable-xft
ac_add_options --enable-crypto
ac_add_options --enable-single-profile
ac_add_options --enable-extensions=all
ac_add_options --enable-reorder
ac_add_options --enable-strip
ac_add_options --enable-strip-libs
ac_add_options --enable-cpp-rtti
ac_add_options --enable-nspr-autoconf
ac_add_options --enable-xterm-updates
ac_add_options --enable-optimize
ac_add_options --enable-elf-dynstr-gc
ac_add_options --enable-mathml
ac_add_options --disable-calendar
ac_add_options --disable-ldap
ac_add_options --disable-installer
ac_add_options --disable-tests
ac_add_options --disable-debug
ac_add_options --disable-dtd-debug
ac_add_options --disable-freetype2
ac_add_options --disable-logging
ac_add_options --disable-pedantic
ac_add_options --disable-mailnews
ac_add_options --disable-composer
ac_add_options --disable-profilesharing
ac_add_options --disable-svg
ac_add_options --disable-jsd
ac_add_options --disable-accessibility
ac_add_options --disable-toolkit-qt
ac_add_options --disable-toolkit-xlib
ac_add_options --disable-toolkit-gtk
do official mozilla.org builds exhibit this problem?  I would suspect no.

Note: you shouldn't build typeaheadfind with Firefox, it causes unexpected
results, since we have a modified TAF impl for the find toolbar.
(In reply to comment #1)
> do official mozilla.org builds exhibit this problem?  I would suspect no.
> 
> Note: you shouldn't build typeaheadfind with Firefox, it causes unexpected
> results, since we have a modified TAF impl for the find toolbar.

Building Firefox without typeaheadfind (removed typeaheadfind from
-enable-extensions line) produced same result. Still not working, that is.

I'm unable to use the official builds since they requier libstdc++5 and I only
have libstdc++6 on my system.
You realize, of course, that you have ac_add_options --enable-extensions=all
after your first enable-extensions line in your listed mozconfig, right?  Please
kill that line and rebuild, then test again.  If it still fails, please post
your about:buildconfig output (as a text file attachment please).
My apologies for missing the --enable-extensions=all
Now everything works as it should!

Sorry for taking your time on this.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.