Comment #43 on issue 150 by thomas.ostergaard: Type-ahead-find
http://code.google.com/p/chromium/issues/detail?id=150
It seems there is a misconception that this feature is only used for
searching for
text on web pages (same as ctrl-f in other browsers). I believe most if not
all the
dissapointed comments here originates from people who use it the same way I
do, for
much faster link navigation.
This means the user have enabled accessibility.typeaheadfind.linksonly as
well as
accessibility.typeaheadfind in about:config in FF.
You can then start typing something from a text link on a page, the browser
will
continusly highlight links matching the entered keys (ctrl-g to jump to
next match)
and when the desired link is highlighted, press enter to follow the link.
For regular
text search, a different key have to be pressed for ctrl-f functionality
("/" in Firefox)
When you already know the layout and links on webpages - like, say, your
workplace's
intranet documentation - this way of navigating is MUCH faster than using a
mouse. I
think I need to state this clearly:
GOOGLE CHROME FEELS LIKE A SLOW BROWSER TO ME BECAUSE OF THE LACK OF
TYPE-AHEAD-FIND
It doesn't matter much if the browser renders the page in 0.1 instead of
0.2 seconds
if you then use 3 seconds instead of 1 scrolling down to select the link
you want to
follow.
To me, the fact that this way of navigating reduce the risk of getting
carpal tunnel
syndrome and sore shoulders is secondary to the fact that type-ahead-find
is simply
much faster. And despite being a big fan of google products and keen on
adopting new
technology I don't think I would ever be able to switch to a browser that
doesn't
have it.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
