Closed
Bug 440293
Opened 17 years ago
Closed 11 years ago
when saving a library search, details on bottom of page are from the previous selection
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: www_king, Unassigned)
Details
Attachments
(1 file)
|
101.26 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0
if you open the library, do a search and save it, the details pane at the bottom of the window shows information of the previous selected item, not of the current saved search.
Reproducible: Always
Steps to Reproduce:
1. open the library
2. do a search in the search toolbar
3. click on the save button
4. enter a name and confirm
Actual Results:
current search result is showed on the top pane, but in the details pane at the bottom, last selection information are showed!
Expected Results:
show the actual selection's information (name of saved search)
Comment 1•17 years ago
|
||
Comment 2•17 years ago
|
||
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
I can reproduce, I'm adding a screenshot "After hitting save for NewSave"
It shows what happens when you save a search from the Bookmarks toolbar -> the save folder for the search is now selected in the left column but the info at the bottom of the library window still show the original location for the search.
Found no other report.
Also reproduced on Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Changing severity to trivial.
Severity: normal → trivial
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•11 years ago
|
||
the save search feature has gone, it may re-appear in future but the code may be so different that it's not worth to keep its old bugs around.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•