418959 - The bookmark manager selects a default menu folder within an imported safari bookmarks folder!

Status: VERIFIED WORKSFORME

(Camino Graveyard :: Bookmarks, enhancement)

Description

[Jo Edward Davidson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.12) Gecko/20080206 Camino/1.5.5
Build Identifier: Camino/1.5.5 (Macintosh; U; Intel Mac OS X Mach-O; en; rv:1.8.1.12) Gecko/20080206 Camino/1.5.5

Now that I know how it worked I was able to move my new bookmark to the correct location so that when I click on the Bookmarks menu, I do see the new bookmark. Now that I read this it looks more like an enhancement request. Sorry about that. New to your project.

Reproducible: Always

Steps to Reproduce:
1.Use an intel MAC running 10.4.11
2.Go to any site U want to bookmark, after importing safari bookmarks.
3.click ADD button Don't navigate to the correct folder before clicking the ADD button.
Actual Results:  
When at first I clicked on the Bookmarks menu, I didn't see the desired bookmark, and wrongly concluded that the bookmark had not been saved

Expected Results:  
The bookmark was saved to an obscure folder

I believed it should have saved the new bookmark in the menu folder so that when U click on th Bookmarks menu, the new bookmark would be seen in the drop down list

Comment 1

[Chris Lawson (gone)]

Hrm. I wonder if we're setting the "last used" bit on the folder holding imported bookmarks somehow. That would be a logical explanation for this behaviour and is probably not the "right" thing to do.

cl

Comment 2

[Stuart Morgan]

I started with a clean profile, imported Safari bookmarks, and then tried to
bookmark a page, and the default was still the bookmark bar, as we ship it.
Unless I'm misunderstanding the STR, I can't reproduce this.

The Bookmark Current Page dialog defaults to the last place that you set it to;
had you manually changed the popup in that dialog to the folder it is currently
defaulting to?

Comment 3

[Stuart Morgan]

Per email, the default was manually changed to what turned out to be the wrong folder, so this is expected behavior; closing WFM.

For what it's worth, this very understandable source of confusion will go away once we address bug 370912.