clearing search bar form history doesn't provide any visible feedback

NEW
Unassigned

Status

()

defect
P5
normal
Rank:
55
5 years ago
4 years ago

People

(Reporter: elgatotitou, Unassigned)

Tracking

27 Branch
Points:
2
Dependency tree / graph
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bug][fxsearch])

Attachments

(1 attachment)

Reporter

Description

5 years ago
Posted image screenshot_246.jpg
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424

Steps to reproduce:

When we try to clear the history search it seems to be okay with FF22 in the menu it goes to "grey" (the text cannot be clicked. That is a "confirmation" it's cleared)


Actual results:

Since FF23 to the lastest stable 27.0.1 the problem is that it doesn't go to grey (you'll see on the screenshot cause my explain could not be perfect). The history search is cleared but no change for the text.


Expected results:

Normally it must do like Firefox 22 so the text goes to grey when the history search has been cleared.
Reporter

Updated

5 years ago
Hardware: x86 → x86_64

Comment 1

5 years ago
This is reproducible in Firefox stable, beta, Nightly, and Aurora.
Status: UNCONFIRMED → NEW
Component: Untriaged → Search
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86_64 → All
This is fallout from http://hg.mozilla.org/mozilla-central/rev/555f2b757639#l8.92

We can't tell synchronously that there's no more history to clear, so we just punted and always assumed there was.

I don't think there's any good way for us to fix this, short of keeping track of form history "dirty" state out of band with notifications and such. That seems like more trouble than it's worth...
Summary: clear history search (from the right by search Engine) → clearing search bar form history doesn't provide any visible feedback
the FormHistory component could expose an async method to tell if there's any data and the menuitem could be initially disabled and then enabled asynchronously if there's data.
ops, I said form history but I meant search service :/
It would actually be form history in this case. That's kind of where I was going with "keeping track of form history "dirty" state out of band with notifications and such", but I'm just not sure it's worth the effort.
Reporter

Comment 6

5 years ago
For the most people which use Firefox "normally" this problem doesn't matter .. A little problem like this could be complicated to resolve ?
Flags: firefox-backlog+
Whiteboard: p=2

Comment 7

5 years ago
I have the same problem !
Reporter

Comment 8

5 years ago
After few beta updates, and lastests release nothing change.. Always this problem .. Firefox 31 beta 1 is still the same ..
Reporter

Comment 9

5 years ago
I've just updated to FF32 candidate 1 but it's a deception :( still nothin ...
Points: --- → 2
Whiteboard: p=2

Updated

4 years ago
Rank: 55
Priority: -- → P5
Whiteboard: [bug][fxsearch]
You need to log in before you can comment on or make changes to this bug.