Open Bug 395637 Opened 17 years ago Updated 2 years ago

sort alphabetically, but with common types on top, in Applications prefpane

Categories

(Firefox :: File Handling, defect, P3)

defect

Tracking

()

People

(Reporter: myk, Unassigned)

References

Details

(Whiteboard: [contentHandling-ui])

Attachments

(2 files)

faaborg's review in bug 377784, comment 45 says we should sort the Applications prefpane so that the Web Feed item is on top followed by the rest of the entries in alphabetical order by type name. In bug 377784, comment 46, mconnor asks, "Why not mailto and others? Kinda hard for me to justify feeds getting prime placement except to aid transitioning users...". In bug 377784, comment 48, faaborg responds, "All of the groups will be on top, once we have them implemented (like calendar = .ics, webcal://, hCalendar). Feeds may eventually become a group if we start to tell the difference between a blog, podcast and video cast. I agree that we should move mailto: into the top section of commonly used applications."
Depends on: 377784
Assignee: nobody → myk
Priority: -- → P2
Target Milestone: --- → Firefox 3 M9
We want to include the "always ask" items, so the only way to avoid them getting in the way is to create an artificial order, with the most relevant items on top. The top section should also include items like PDF, and mailto. Ideally the content types under the predetermined top section would be sorted by how often the user encounters them. But since this is out of scope, we are falling back to alphabetical. Note that I think alphabetical order of the applications much more useful than alphabetical order of the content types. This is because at least then related types will be listed together, and users probably think about applications more than they think about (or know of) content types.
> Note that I think alphabetical order of the > applications much more useful than alphabetical order of the content types. > This is because at least then related types will be listed together, and users > probably think about applications more than they think about (or know of) > content types. If we sort by application name rather than type name, then, when a user selects a new application from the dropdown menu, the selected entry will jump to a different place in the list, which seems like an unexpected and disturbing behavior.
Whiteboard: [contentHandling-ui]
>the selected entry will jump to a >different place in the list, which seems like an unexpected and disturbing >behavior. Yeah, I was imagining that the sort would only occur when the UI was being generated, so the recently changed items would remain in place until you opened the prefpane again.
mconnor, any additional thoughts on this?
Requesting wanted-1.9 for this Applications prefpane polish fix.
Flags: blocking-firefox3?
Why are the groups on top? I don't know if that makes any sense to me. I thought the point of groups was to coalesce multiple similar items for simpler management. That doesn't argue for elevating them higher than other items, they're just an item with special properties, but I don't think it'll make sense if Web Feeds is first, and the rest are in alphabetical order...
>Why are the groups on top? I don't know if that makes any sense to me. I proposed that before we also considered using groups to reduce the complexity of plugins. Just being a group isn't enough, we should only promote common types. (Changed summary from "Web feed" to "common types.") We should push PDF, email and other common types up in the list as well. The overall goal is to let the user find the type of content they want to edit without having to scroll through a long list of unrecognizable mime types.
Summary: sort alphabetically, but with Web Feed on top, in Applications prefpane → sort alphabetically, but with common types on top, in Applications prefpane
Flags: blocking-firefox3? → blocking-firefox3-
Whiteboard: [contentHandling-ui] → [contentHandling-ui][wanted-firefox3]
This bug needs someone to make a decision.
Whiteboard: [contentHandling-ui][wanted-firefox3] → [contentHandling-ui][wanted-firefox3][ui-wanted]
Rerequesting blocking-firefox3 and uiwanted because principals are disagreeing in comments on the bug, and we need a decision on this issue to be able to move forward to fixing (or wontfixing) it.
Flags: blocking-firefox3- → blocking-firefox3?
Whiteboard: [contentHandling-ui][wanted-firefox3][ui-wanted] → [contentHandling-ui][wanted-firefox3]
Blocking for ui decision, will circle back by tomorrow, if I haven't, please do yell at me.
Flags: blocking-firefox3? → blocking-firefox3+
Target Milestone: Firefox 3 M9 → Firefox 3 M10
Not a blocker, might still do this (undecided).
Flags: blocking-firefox3+ → blocking-firefox3-
Here is what this prefpane looks like by default on Windows, OS X and Linux. Currently we only include two items "Web Feed" and "webcal" (we are also going to include mailto: right?). OS X picks up PNG and TIFF through Quicktime, and Windows has a few Windows Media Player items. If you add flash, you pick up an additional 2 items.
While the default view (in the previous attachment) is fine, this is what I am worried about, a very long list of MIME types that aren't really human readable, and all appear to be mostly the same (in this case application/x-java-applet*) takes over the first view. If the user is looking for "Web Feed" they may give up before touching the scroll bar, scared off by the initial onslaught of technobabble.
Flags: wanted-firefox3+
Whiteboard: [contentHandling-ui][wanted-firefox3] → [contentHandling-ui]
Without knowing whether or not we're going to do this, it's hard to target the doing of it.
Target Milestone: Firefox 3 beta2 → ---
If it helps to move the decision making process along at all, I'm still totally in favor of us doing this.
If I put together a list of types we would like sorted to the top, could someone prepare a patch?
Removing uiwanted since it's unlikely that this bug is a priority until we look at how we handle application mappings again. No activity since 2008. :)
Keywords: uiwanted
Assignee: myk → nobody
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: