Closed
Bug 894381
Opened 12 years ago
Closed 12 years ago
FindBar buttons should be enabled when moving tab between windows
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox 25
People
(Reporter: alice0775, Assigned: unusualtears, NeedInfo)
References
Details
Attachments
(1 file, 1 obsolete file)
|
2.01 KB,
patch
|
Details | Diff | Splinter Review |
Build Identifier:
http://hg.mozilla.org/mozilla-central/rev/5976b9c673f8
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20130715 Firefox/25.0 ID:20130715211256
Steps To Reproduce:
1. Open any page
ex. https://developer.mozilla.org/en-US/docs/Code_snippets
2. Open FindBar and type "mozilla"
3. Detach the tab
4. Click Up/Down arrow in the FindBar
Actual Results:
Nothing happens
Expected results:
Find prev/next should be performed
| Reporter | ||
Updated•12 years ago
|
Summary: FindBar stops workig after detached tab in the state that opened FindBar → FindBar stops working after detached tab in the state that opened FindBar
Thanks Alice!
Bug 890595 fixed this for other cases, but when we move a tab to a different window, we open the findbar without running findbar.startFind(). This does it via findbar.onFindCommand() after we set the _findField.value.
Also adds a test.
Summary: FindBar stops working after detached tab in the state that opened FindBar → FindBar buttons should be enabled when moving tab between windows
Updated•12 years ago
|
Attachment #777464 -
Flags: review?(dao) → review+
Pushed to try: https://tbpl.mozilla.org/?tree=Try&rev=d3d165876c5d
Attachment #777464 -
Attachment is obsolete: true
Keywords: checkin-needed
Comment 3•12 years ago
|
||
Flags: in-testsuite+
Keywords: checkin-needed
Comment 4•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 25
Updated•12 years ago
|
QA Contact: manuela.muntean
Comment 5•12 years ago
|
||
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 the prev/next is performed in the de-attached window.
The search however, is not always accurate, sometimes choosing prev/next in the de-attached window will select the first result in the page, and not the precedent/subsequent outcome of the result found before detaching the tab.
Is this the expected behavior or should I file a new bug for this? Thank you
Flags: needinfo?
You need to log in
before you can comment on or make changes to this bug.
Description
•