User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: In TB 2 the blue close button disappears, when the search string is killed by klicking this button. So there is an optical feedback that no search filter is active. In TB 3 this button only disappears when the search string is killed via keyboard (backspace). A mouse click clears the search string field, but the button is still to see and one thinks that the search filter is still active. Reproducible: Always Steps to Reproduce: 1. In the main window enter a search string in the search field 2. Clear the text by clicking the blue close button -> button remains: wrong! 3. Now enter a sting and use the backspace to kill it -> button disappears: ok!
Yes, it is: the behavior is changed from TB 2.x. Ludo we should ask to :clarkbw if this should be close as wontfix?
Why "wontfix"? The button disappears after clearing the text via backspace, but it remains after using the mouse. That is inconsequent.
You are right franz: is inconsistent behavior because when user click on button input text is cleaned but button still reamains visible. I don't know if this is deliberate.
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → Search
Ever confirmed: true
QA Contact: front-end → search
You need to log in before you can comment on or make changes to this bug.