Closed Bug 250313 Opened 21 years ago Closed 21 years ago

display "match case" option for Find Toolbar

Categories

(Toolkit :: Find Toolbar, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: bugzilla)

References

Details

(Keywords: fixed-aviary1.0)

the Find dialog had a checkbox for matching case, and while the Find Toolbar has a means(*) of matching case, it isn't obvious. (*)iirc: if lower-case chars are entered, then find is case-insensitive. but when an upper-case char is entered, then the find becomes case-sensitive (does this state start with the first upper-case char typed in?). question: what would happen if the user want to find something that was soley in lower-case?
QA Contact: firefox.general → bugzilla
Summary: have "match case" option for Find Toolbar → display "match case" option for Find Toolbar
-> Find Toolbar component.
Component: General → Find Toolbar / FastFind
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0?
Minusing this for now. Mike, if you can create a patch that does a case-sensitive find if there's a capital letter in the find string, I'll take it.
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0-
*** Bug 261868 has been marked as a duplicate of this bug. ***
What if I'm searching for a lowercase string and there would be thousands of false positives with mixed or uppercase? If it's a regression for enough users, it may be a regression worth fixing. Any loss of functionality is a regression in plain English, but some may be worth the gain in simplicity. I don't see that win here -- the Find toolbar is neither simple nor out of control with options. There is no mitigation from faster find, and not enough from uppercase secretly triggering case-sensitivity. That kind of implicit option can confuse people badly, even as it doesn't solve the lowercase-only match problem. /be
Flags: blocking-aviary1.0- → blocking-aviary1.0?
lets try and get this fixed.
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
This shouldn't have any localization impact because a string is available from http://lxr.mozilla.org/seamonkey/source/toolkit/locale/finddialog.dtd (I think).
Fixed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
see regression bug 264789.
also see bug 264801.
fixed-aviary flag?
Keywords: fixed-aviary1.0
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.