Closed Bug 303612 Opened 19 years ago Closed 16 years ago

clearing search bookmarks does not produce the correct display

Categories

(Firefox :: Bookmarks & History, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ljbmailprotect-mozilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Clearing (or undoing) the 'search bookmarks' field in the bookmarks manager does
not restore the display to the original view of the bookmark folders.  Instead,
it displays a random folder deep in the bookmark tree.

Reproducible: Always

Steps to Reproduce:
1. open bookmarks manager
2. click on the topmost folder 'bookmarks' (or any other folder)
3. fill out the search field
4. clear the search field by backspacing, deleting or right clicking 'undo'
Actual Results:  
The wrong folder view is displayed

Expected Results:  
The displayed view after step 4 should be identical to step 2.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050805 Firefox/1.0+
ID:2005080513

This seems to have been fixed in the latest builds. Can you confirm?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
(In reply to comment #1)
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050805 Firefox/1.0+
> ID:2005080513
> 
> This seems to have been fixed in the latest builds. Can you confirm?
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

I don't have a test machine to try out a nightly build on.
Can someone else confirm this using the simple test procedure I outlined above?
Version: unspecified → 1.0 Branch
This is WORKSFORME on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1b3pre) Gecko/20090107 Shiretoko/3.1b3pre RTSE/1.1.0.20081207 ID:20090107020449
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.