GNOME Bugzilla – Bug 157435
no typeahead with the firefox backend
Last modified: 2005-02-22 16:10:27 UTC
Apparently firefox doesn't use the typeahead mode anymore but the findbar. Activating the typeahead breaks the findbar (and the typeahead seems to doesn't even work correctly with the current version) so most of the distributions have turned it off. Is there any way to get a typeahed working in epiphany even if firefox has turned this off ?
*** Bug 162198 has been marked as a duplicate of this bug. ***
Created attachment 36215 [details] [review] make typeaheadfind extension co-exist with firefox find-as-you-type Apply this patch to firefox source, cd extensions/typeaheadfind and make install. It fixes the typeaheadfind extension not to conflict with firefox' typeaheadfind. Made from firefox trunk, but should apply to aviary branch (ff 1.0 branch) too; if not, it's easy to adapt manually since it's just a s/TypeAheadFind/TypeAheadFindSea/g (and case variations) sed job.
I forgot to mention that you'll have to create "accessibility.typeaheadfindsea" pref and set to 'true' in epiphany's about:config.
Created attachment 36240 [details] [review] epiphany default pref.js patch to go with the firefox patch
Created attachment 36359 [details] [review] updated firefox typeaheadfind patch fix two places where I didn't add the "sea" suffix. Compiling firefox with --enable-extensions=typeaheadfind,default produces a ff (trunk) build with working typeaheadfind here, and makes typeahead work in ephy.
Created attachment 36360 [details] [review] updated firefox typeaheadfind patch without debug printfs Remove stray debug output too.
The latest patch corrects in particular the contract ID of the typeaheadfind extension not to use the same as firefox internal typeaheadfind. I think the reason it worked for me before was install/registration order. It should work now everywhere. Can someone please test and report back? Thanks.
works fine now, thanks !
Comment on attachment 36240 [details] [review] epiphany default pref.js patch to go with the firefox patch Committed on HEAD and gnome-2-8.
should we close this bug now ? The spaces don't work in the typeahead (https://bugzilla.ubuntu.com/6013), should I open a bug for this ?
Yes, we can close it. I think we should have a "Release notes" section on the wiki perhaps documenting this. The bug with spaces has nothing to do with this typeaheadfind hack, since I can reproduce it also in epiphany using mozilla trunk (but neither in mozilla itself, nor in testgtkembed). So that deserves a separate bug.
bug closed so, I've opened #165811 about the space issue
chpe, maybe this could just be an FAQ question?
Not sure, FAQ is more for end users isn't it?
Created attachment 37783 [details] [review] also set accessibility.typeaheadfindsea.autostart You only need this patch for Epiphany 1.4.x