Closed Bug 561535 Opened 14 years ago Closed 14 years ago

Quickfilter non-functional if the Welcome page appears on run (e.g. after an update)

Categories

(Thunderbird :: Search, defect)

defect
Not set
normal

Tracking

(thunderbird3.1 beta2-fixed)

RESOLVED FIXED
Thunderbird 3.1b2
Tracking Status
thunderbird3.1 --- beta2-fixed

People

(Reporter: rimas, Assigned: asuth)

References

Details

Attachments

(1 file)

Mozilla/5.0 (X11; U; Linux i686; lt; rv:1.9.2.5pre) Gecko/20100423 Lanikai/3.1b2pre

Instead of focusing the quick search bar, Ctrl+F opens the in-message search bar.
Blocks: filterbar
It's supposed to toggle between them.  If your focus is not in the quick filter bar text filter, it should focus the quick filter bar text filter.  If your focus is in the quick filter bar text filter, it should focus the in-message search bar.

Is this not what you are seeing?
Nope, it doesn't toggle. Just opens the in-message search or selects all text in it's input box if it already has focus.
QA peeps, can you magic this some?

We actually have mozmill tests for this case, so I am presuming there are some extenuating circumstances not immediately obvious to me.
WFM on vista, today's nightly
WFM on WinXP trunk, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100423 Shredder/3.2a1pre
Rimas can you try in -safe-mode ?
Wow!
Not only does it work in safe mode, but it ALSO works in normal mode after safe mode!

Furthermore, until I ran in safe mode, I didn't see the quickfilter bar toggle button, and the quick filter bar itself was totally ineffective (not working). Now the toggle button is there, and the filter works.

Any clues why?
something got borked somewhere and was restored because of the use of safemode. if you have your previous locastore.rdf file that might help ? have you been running the extension - before the toolbar made it into core TB ?
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
No, I don't have the localstore.rdf, and I wasn't using the extension either. I was running stable series before.
Possibilities explaining the problem include:
- You were previously using the extension and the extension fought the built-in version.
- You tried some of the try builds which did something that caused the next bullet point...
- The tab de-persistence code has a bug in it that only happens with certain sessionstore.js scenarios.  

I would just keep this issue in mind in case we start getting more reported cases...
Ha! I just managed to repro by:
1) Quitting Lanikai
2) Launching Thunderbird 3.0.x
3) Quitting Thunderbird
4) Launching Lanikai
5) Closing the Welcome tab that appeared

That's it! Until I restarted Lanikai, I couldn't use the quickfilter bar. Same happens in safe mode, BTW. I'm pretty sure that the Welcome tab is the reason, because while I'm in it, I see the nonfunctional quickfilter toggle button, but after I close it, the button disappears.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Ctrl+F does not focus the quick search bar → Quickfilter non-functional if the Welcome page appears on run (e.g. after an update)
anything in the error console?
Nothing relevant :(
Thanks very much for the STR on this!

A slightly revised set of STR is:
0) have thunderbird not be running
1) delete your session.json file from your profile
2) edit user prefs so that the "mailnews.start_page_override.mstone" pref is not whatever it already is.

The general problem was that because the QuickFilterBar was getting initialized at an arbitrary time (using a "load" event) after the first tab was already opened, it was producing a synthetic tab notification somewhat unsafely.  It ended up lying to itself and claiming that the welcome page tab was the first 3-pane tab.  As such, the quick-filter bar would never be available on the first tab.  (There may be fallout for new tabs opened too because of errors with inheritance because a fundamental invariant would already have been violated; don't know.)

The fix is to explicitly initialize the quick filter bar with the rest of its brethren so it can avoid generating synthetic events.  (It is possible, of course, to generate safe synthetic events, but why add more code when you don't have to?)

This would be pretty hard to test realistically in mozmill without giving it its own test directory with just the single test.  Since thunderbird startup times are not fast, I think that's more expensive than justified given that this patch fundamentally simplifies the logic so the buggy situation can no longer arise.
Assignee: nobody → bugmail
Status: REOPENED → ASSIGNED
Attachment #442095 - Flags: review?(bugzilla)
Attachment #442095 - Flags: review?(bugzilla)
Attachment #442095 - Flags: review+
Attachment #442095 - Flags: approval-thunderbird3.1?
Checked in to trunk:
http://hg.mozilla.org/comm-central/rev/fbb7edba8ed5

c-1.9.2:
http://hg.mozilla.org/releases/comm-1.9.2/rev/eea8cb36da17

3.1 beta 2 branch for build 2 of beta 2:
http://hg.mozilla.org/releases/comm-1.9.2/rev/0f8f9c6d052c
Status: ASSIGNED → RESOLVED
Closed: 14 years ago14 years ago
OS: Linux → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.1b2
Attachment #442095 - Flags: approval-thunderbird3.1? → approval-thunderbird3.1+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: