After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141963 - Find as you type should be off by default
Find as you type should be off by default
Status: RESOLVED OBSOLETE
Product: epiphany
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
needs-forwarding
: 314752 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-05-05 21:50 UTC by André Dahlqvist
Modified: 2007-05-31 12:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Dahlqvist 2004-05-05 21:50:22 UTC
I think the feature "Find as you type" should be off by default in Epiphany. The
reason I think so is that it is an advanced feature which is unfortunately quite
easy to trigger it by misstake. If it is triggered by misstake it is difficult
for a newbie (as well as an experienced user who just doesn't know about the
feature) to know what is going on and how to get out of it.

I myself have triggered "Find as you type" by misstake several times. It has
happened when I have missed a form field with the mouse cursor (causing the page
body being focused instead of the form field) and I haven't noticed it until I
have started typing. When you do this, Epiphany starts searching for links
matching whatever you intended to write in the form field and it will beep if it
doesn't find it. If you're unlucky, what you just typed matches a link further
down the page an focus jumps to that place.
Comment 1 spark 2004-05-06 08:35:32 UTC
I vote wontfix. This is an important accessability feature.
Comment 2 André Dahlqvist 2004-05-06 11:02:41 UTC
As a compromize, can it be changed to require a keyboard combination to start
it? That way the accidental starting of it is avoided, but people requiring
accessibility can still easily start it.
Comment 3 Marco Pesenti Gritti 2004-05-20 19:12:41 UTC
I agree with xan. Andre improvements to this functionality needs to be done in
mozilla itself, because we just inherit it.
Comment 4 Christian Persch 2004-05-20 19:29:00 UTC
Hm, mozilla already has that functionality. The pref is
"accessibility.typeaheadfind.autostart". If you set it to "false" in
about:config, you have to explicitly start a find with / (text) or ' (links).
Comment 5 Marco Pesenti Gritti 2004-05-23 15:54:39 UTC
IHMO we should stay we the default. But I'm ccing Calum and Bill about it 
since it's an accessibility issue.
Comment 6 bill.haneman 2004-05-24 10:10:18 UTC
why is this "an important accessibility feature" ?  As far as I can see, the
feature actually causes problems for screenreader users.
Comment 7 Marco Pesenti Gritti 2004-05-24 17:24:13 UTC
Because mozilla people claim it I guess :)

From http://www.mozilla.org/products/firefox/why/

"Firefox also features sophisticated 'Type-Ahead Find' for links that make it
easier for users with accessibility needs (such as those using screen readers,
or even laptop users with inconvenient pointing devices) to select links. Simply
start typing the name of the link that you want to select and Firefox will shift
focus to it."

I'd have no problems to disable autostart, if you think it's the better thing to
do accessibility wise.

Thanks a lot for the feedback, Bill.
Comment 8 bill.haneman 2004-05-24 18:19:02 UTC
It's true that some sort of link-navigation that doesn't require the mouse is a
must for the default configuration.  I suppose the type-ahead find ia one way to
do this, but it obviously has some side-effects when entering forms (the initial
comment in this bug report).  Having a keyboard shortcut for enabling typeahead
sounds like a very good idea however, since for some users I agree that the
typeahead find will be an important accessibility aid.  I am not sure how well
it serves screenreader users however.

Comment 9 Calum Benson 2004-10-04 16:51:15 UTC
I'd probably vote for disabling autostart too.  I'd be keen to try and make the
typeahead feature more discoverable than it is in Mozilla, though (although I
don't have any great ideas as to how)-- I only found out that I could use / to
search in Mozilla by accident, and I had no idea I could use ' for links until I
read Christian's comment there just now...
Comment 10 Christian Persch 2004-10-13 10:51:54 UTC
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
Comment 11 Christian Persch 2005-01-23 13:38:51 UTC
Fixed in HEAD.
Comment 12 Christian Persch 2005-02-01 20:32:21 UTC
I had to back this out since it caused bug 165811.
Comment 13 bill.haneman 2005-02-01 23:07:49 UTC
It looks to me as if the patch had a logic error.  Are you planning to find+fix
that error, then reinstate this patch?

 I think we're agreed that typeahead find should be off by default...
Comment 14 Christian Persch 2005-02-01 23:23:44 UTC
We've uncovered a mozilla bug with that (see bug 165811), so I don't think we
can re-disable this anytime soon.
Comment 15 Lionel Dricot 2005-04-12 15:03:36 UTC
The firefox behaviour is to enable typeahead when you press "/".

This is a really good behaviour, IMHO. 

Is it possible for Epiphany to use it too ?  It would be nice for both opinions.
Comment 16 Christian Persch 2005-05-28 23:15:03 UTC
This is fixed in cvs. Leaving open because we still need to file a bug report
upstream in mozilla.
Comment 17 Christian Persch 2005-08-30 11:02:12 UTC
*** Bug 314752 has been marked as a duplicate of this bug. ***