Currently, if the user begins a Find in Page search, this menu persists if they open a new window. This behavior assumes the user will be continuing their search task in a new window. The unintended consequence is that the Find in Page toolbar remains constantly open, adding to the Firefox UI's visible chrome, while providing little benefit to the user. Reopening the Find in Page toolbar is trivial if the user does want to continue to search, but remembering to close Find in Page seems to be a task rarely undertaken, leading to Find in Page constantly being open. Reproducible: Always Steps to Reproduce: 1. Start Firefox 2. Press Control-F 3. Press Control-N Actual result: new window has Find in Page Toolbar at bottom Expected result: new window does not have Find in Page Toolbar at bottom
This is a subset of bug 537013, perhaps a dup if we're certain fixing bug 537013 is the way to go.
Component: Toolbars → General
QA Contact: toolbars → general
Created attachment 448479 [details] [diff] [review] don't inherit the find bar to new windows bug 537013 can be evaluated separately
Assignee: nobody → dao
Status: NEW → ASSIGNED
Attachment #448479 - Flags: ui-review?(faaborg)
Comment on attachment 448479 [details] [diff] [review] don't inherit the find bar to new windows This is fine, but per tab is the way to go. If we would rather just check that change in to streamline this that's fine.
Attachment #448479 - Flags: ui-review?(faaborg) → ui-review+
Attachment #448479 - Flags: review?(mano) → review?(gavin.sharp)
Attachment #448479 - Flags: review?(gavin.sharp) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a6
While testing for the pre-beta sign-off of the Find Bar Redesign feature, I tried to verify this bug with the latest Aurora (build ID: 20130903004001), and this works as expected on Win 7 64-bit, Mac OS X 10.7 and Ubuntu 13.04 32-bit. Find in page doesn't persist in a new window.
Status: RESOLVED → VERIFIED
QA Contact: manuela.muntean
You need to log in before you can comment on or make changes to this bug.