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 81293 - "Find text" UI improvement ideas...
"Find text" UI improvement ideas...
Status: RESOLVED DUPLICATE of bug 109257
Product: galeon
Classification: Deprecated
Component: User interface
0.x
Other other
: Normal enhancement
: ---
Assigned To: galeon-maint
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2002-05-09 23:09 UTC by Ben FrantzDale
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ben FrantzDale 2002-05-09 23:09:04 UTC
Some ideas:

(1) "Match upper/lower case" is a bit confusing... e.g.: does it mean
"match both upper and lower case" or does it mean "match the
upper/lower-caseness of things". One thought: "Match exact upper/lower
case".  (The problem seems to be  a lack of a word for
"capital/lowercaseness".)


The rest of these may relate to Mozilla more. I'm not sure how much Galeon
can control Mozilla.
(2) When the page contains no hits, both the Prev and Next buttons should
be insensative. Also a tooltip for them like ``No Matches'' would ne nice.

(3) Galeon could run the search as the query was typed in, then  the
next/prev buttons could go grey before someone finished entering a failing
search.

(4) The matches on a page could be remembered. For very long pages,
searching takes a few seconds. By remembering the matches, percieved search
speed would go up.
Comment 1 Crispin Flowerday (not receiving bugmail) 2003-09-24 21:21:21 UTC
This wont be fixed for the 1.2.x series

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