Open Bug 416555 Opened 17 years ago Updated 2 years ago

when sorting by name in the Library put folders before bookmarks

Categories

(Firefox :: Bookmarks & History, defect, P5)

defect

Tracking

()

People

(Reporter: mak, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [needs new patch])

Attachments

(1 file, 1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
when sorting by name in the Library we are mixing up bookmarks and folders. It would be more useful and common put folders before (see also Bug 400474 from where this was spunoff)
Attachment #302305 - Flags: review?(dietrich)
adding uiwanted to be sure this is a wanted change. We are already sorting with folders before when sorting the menu by name so it should be the preferred way of sorting (also for platform conformity)
Keywords: uiwanted
That's the way how Firefox 2 is sorting by name. Adding regression keyword.
Flags: blocking-firefox3?
Keywords: regression
Assignee: nobody → mak77
Low priority blocker to fix the UE regression here, which could be pretty annoying. To clarify, though, when we do this sort, is it permanent or not in terms of ordering the items? I know we've run into that question before, and believe that the solution was that sorting them wouldn't re-order them permanently.
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P3
no, it's not permanent
Keywords: uiwanted
Status: NEW → ASSIGNED
As note: This only happens when doing that via the Views menu. Choosing "Sort by name" from within the context menu does the sorting right.
Priority: P3 → P4
Attached patch unbitrotSplinter Review
Attachment #302305 - Attachment is obsolete: true
Attachment #307183 - Flags: review?(dietrich)
Attachment #302305 - Flags: review?(dietrich)
Whiteboard: [has patch] [needs review Dietrich]
Not blocking on this bug for final ship. Would take a safe enough patch if one comes through.
Flags: wanted-firefox3+
Flags: blocking-firefox3-
Flags: blocking-firefox3+
Hrm. I'd prefer to implement a sorting callback, rather than continue to add special-case sorting code to the back-end. We should use the mechanism in the link below for a new nsINavHistoryQueryOptions.sortingFunction option. That would allow more extensibility and customization, and we can stop chasing use-cases in C++. http://developer.mozilla.org/en/docs/Creating_JavaScript_callbacks_in_components
Attachment #307183 - Flags: review?(dietrich)
Some of us _like_ mixing folders and files in a sort. Can this be made an option?
Is this the same as bug 408775?
And the same as bug 288260?
Whiteboard: [has patch] [needs review Dietrich] → [needs new patch]
Blocks: 467848
Flags: in-litmus?
I added the in-litmus flag value "?" to this test case as it's a continuation of bug 400474 which has been verified and fixed (even though the discussion over the fix is ongoing) and its in-litmus flag value was "?".
due to bug 499985 i'm not sure where this will finish. unassigning for now since not working actively on it.
Assignee: mak77 → nobody
Status: ASSIGNED → NEW
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
PLEASE only do this if it is a configuration option. Personally, I don't like the way Windows does this! I LIKE having folders and bookmarks sorted together. OK, that's just me; but making it optional shouldn't make it any harder to do.
Priority: P4 → --
Priority: -- → P4
Priority: P4 → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: