Closed Bug 340747 Opened 18 years ago Closed 18 years ago

Should "Match case" set in normal find mode persist in FAYT mode?

Categories

(Toolkit :: Find Toolbar, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID
mozilla1.8.1beta1

People

(Reporter: Waldo, Assigned: Waldo)

References

Details

(Whiteboard: [swag: 0.5d])

The new minimal find bar UI means that there's no visible indication that case-sensitive searching happens, which can be confusing.  I vaguely remember encountering this problem a couple times before the find bar existed, but the presence of the find bar at least made the problem significantly more obvious while searching.
This is a fairly uncommon situation, but I think this poor UE should be fixed if the minimal find bar UI is to be used in Firefox.
Flags: blocking-firefox2?
Whiteboard: [swag: 0.5d]
There are at least a couple bugs relating to the case sensitivity UI, AFAIK.  I have suggested before that we should switch to doing something like Emacs for case sensitive searching (where we automatically determine whether to do a case-sensitive search based on what the user types), and remove the persistent option from the bar.  That would make the Find bar UI cleaner and solve this bug, and make the user experience easier as well, I think.  (Currently, it's annoying to have to toggle something on to do a case-sensitive search, and annoying to have to remember to toggle it off when done; this bug just makes it yet MORE annoying.)

The specific case-sensitivity behavior I'd like is to be case-insensitive for all-lowercase searches, and case sensitive for mixed-case searches.  I'm not sure which way is better on all-uppercase searches.  Case-sensitive, I think?

For those who need to set things differently, this should probably be controlled by a pref:
0 = never case-sensitive
1 = always case-sensitive
2 = auto-determine [default]

Shouldn't be hard to code in this behavior, it's just a UI question.  It'd be a nice win IMO.
Short answer: "no, it shouldn't". As things exist now with bug 337654 landed, FAYT should always be case-insensitive since there's no way for a user to be able to tell which mode they would be in. If they want to do a case sensitive search, Accel-F awaits their loving touch.

While I agree wholeheartedly with the sentiment of comment 2, it is a bit of a bugmorph. pkasting, can you file a separate bug on that issue, please?
Depends on: 340849
(In reply to comment #3)
> While I agree wholeheartedly with the sentiment of comment 2, it is a bit of a
> bugmorph. pkasting, can you file a separate bug on that issue, please?

Done, see bug 340849.  I think when that is fixed this bug will become INVALID.
Beltzner's right.  FAYT should always be case-insensitive.
Status: NEW → ASSIGNED
Flags: blocking-firefox2? → blocking-firefox2+
Even (once bug 340849 is fixed) in auto-case-sensitivity mode, or when the user says "always case-sensitive"?
I think you're statement in comment 4 is right. When that one is fixed, this one will become INVALID.
Marking INVALID per comment 4 and comment 7.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Flags: blocking-firefox2+
In Firefox 2.0 final, checking the "Match case" button on the full find bar sets accessibility.typeaheadfind.casesensitive to 1.  This contradicts the decision here that it shouldn't.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.