Closed
Bug 210576
Opened 22 years ago
Closed 22 years ago
[Quick Search] "Clear" button always disabled
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tony, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
The "Quick Search" field ("Subject or Sender contains: [_______]") has a "Clear"
button which never appears to be enabled, even when text is in the field.
Reproducible: Always
Steps to Reproduce:
1. Enter text in the field "Subject or Sender contains:".
2. Attempt to click "Clear".
Actual Results:
The "Clear" next to the "Subject or Sender contains: [_______]" field button was
not enabled
Expected Results:
Mozilla should enable the "Clear" button when there is text in the "Subject or
Sender contains: [_______]" field, and disable it when there is no text in this
field.
No additional info.
Hmm. It seems I did slightly misinterpret the button's function; most Windows
applications with a "Clear" button still function the way I suggested, however;
when text is entered, the button should be enabled to allow the user to clear
the field, and accordingly disabled when it's either been used or empty.
My apologies. Severity changed to "Enhancement".
Severity: trivial → enhancement
WFM. The clear button becomes active as soon as quicksearch returns results.
Am I misunderstanding something?
Tony, if the clear button doesn't enable in your installation as I described
(and as you seem to request for an enhancement), then that's a bug, not
enhancement. Are you asking for an enhancement of some sort? If this is a bug,
does it also occur with a fresh profile, or in a new build?
nonresponse -> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search
You need to log in
before you can comment on or make changes to this bug.
Description
•