Closed Bug 428524 Opened 16 years ago Closed 16 years ago

cmd+D and star UI file bookmarks in different places by default

Categories

(Firefox :: Bookmarks & History, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: maikelkrause, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b5) Gecko/2008032619 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b5) Gecko/2008032619 Firefox/3.0b5

When clicking the star icon in the location bar, it sorts the page in "Unfiled Bookmarks" by default. However, when using cmd+D (and I assume ctrl+D on win/linux) the default is the Bookmarks Menu. Cmd+D should file in "Unfiled Bookmarks" instead, for consistancy (and because it's more logical in my opinion).

Reproducible: Always
Component: Bookmarks → Places
QA Contact: bookmarks → places
Version: unspecified → Trunk
This behavior is purposefully designed to be this way. When you click on the star, it just quickly adds it to the Unfiled (Unsorted) Bookmarks folder, which is a bucket for these things. If you hit control-d, you are making a decision to make a bookmark out of it with the full bookmark dialog so you can pick folders, etc. This defaults to the main bookmarks folder because it isn't an unsorted bookmark but longer term one. 

So, this is not a bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
I cannot agree with this design decision and bug resolution. Why would be using keyboard shortcut any different? I am using keyboard a lot for surfing and tend to minimize use of a mouse. And thus I do not see the difference of quickly adding the bookmark with clicking on the star and quickly adding it with pressing the keyboard shortcut. Both should be the same thing, the only difference is which input device do you use. Some prefer mouse, some prefer keyboard.

In any case there should be a way to configure your preference. Also for a star. What if I want to store it by default somewhere else when I click on a star?
OK. So with keyconfig (http://forums.mozillazine.org/viewtopic.php?t=72994) I set keyboard shortcut to:

PlacesCommandHook.bookmarkCurrentPage(true, PlacesUtils.unfiledBookmarksFolderId);

And now it works as I like.
I do not like this behavior myself.
If this is designed to be, then I wish assigning a new shortcut to bring a bookmark window just like the one appeared when I double click the star icon.

new bookmark defaults to unsorted folder is really a good idea, that will keep the Bookmarks drop down menu clean. I used to create a 'temp' folder for that purpose. Since firefox3 does not remember last bookmark folder, it becomes complicated to use 'temp' folder. So why not make the behavior of both 'add bookmark' action the same, or at least add an option to let the user choose where default bookmark goes.

By the way, keyconfig is out-dated on addons.mozilla.org for Firefox 3.0.
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
+1 for the first comment; here on 32.0a1 (2014-06-02)

Before, when I saved via click or keyboard shortcut, it was the same, it recalled the latest folder chosen. 

Now if you click on the start, it automatically saves on "unsorted" and if you use the shortcut, it will saves it on "bookmarks menu".

It should save for both actions the same thing: save on the latest folder chosen; like it did before.
You need to log in before you can comment on or make changes to this bug.