Comment 22 for bug 61002

(In reply to comment #17)
> Whatever bar you choose to use for FAYT, please make it auto-dismiss. IMHO, the
> only redeeming feature of having any type of find bar pop up to block part of
> the content area when I'm keyboard navigating is that it can be safely ignored
> if the bar will go away all by itself.

The Quick Find bar does auto-dismiss. And I think the Find bar doesn't play nicely with auto-dismiss; how can you have a bar with mouse-clickable controls that autodismisses? And certainly the whole point of the visual differentiation was to note that the two modes behaved differently, so we couldn't make the Find bar dismiss when invoked one way and not the other, or we'd just be back at the previous release's state, which got bugs filed due to "why did my bar go away/not go away when I wanted" since people didn't realize there were two modes.

So I think either this bug gets WONTFIXed and you have an autodismissing Quick Find bar, or it gets FIXED and you have a non-dismissing Find bar. Note that the find bar doesn't cover the content on the page, it changes the size of the content area, so nothing is "hidden under the find bar". That means that it _should_ be "safe to ignore".

(In reply to comment #20)
> LOL, that's true -- you busted me. But at least we did have the alternative
> untimed Ctrl+F back then.

And still do

> Will the timer be used to
> dismiss the current Ctrl+F find?

No, the Find bar is very intentionally not auto-dismissed. It can be closed via a close box or the escape key.