Closed Bug 225424 Opened 21 years ago Closed 21 years ago

The View/Apply Theme menu of available themes should be sorted alphabetically

Categories

(Core Graveyard :: Skinability, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.6beta

People

(Reporter: Ilka_Stromberg, Assigned: malcolm-bmo)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5) Gecko/20031007

The  View/Apply Theme  menu of available themes should be sorted alphabetically.

In this day an age any "list"  should be sorted in some sort of sequence so that
what the user is looking for can be found quickly.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Confirmed. To be more specific, both the View > Apply Theme menu and the Themes
preferences panel are in the same, arbitrary order (other than Classic always
being first). As an example, here's the menu as it appears now on my machine, I
just grabbed some random themes to test with.

Classic
American 1.5b
Modern
Toy Factory 1.5b+
Pinball
Assignee: general → skinability
Status: UNCONFIRMED → NEW
Component: Browser-General → Skinability
Ever confirmed: true
OS: other → All
Hardware: PC → All
-> me (I have a patch, will attach in a few hours)
Assignee: skinability → malcolm-bmo
Status: NEW → ASSIGNED
Comment on attachment 135465 [details] [diff] [review]
Sort the theme names in the View/Apply and preferences windows

Requesting review. There's a similar change in Firebird, but I'll attach that
to a separate bug.
Attachment #135465 - Flags: superreview?(alecf)
Attachment #135465 - Flags: review?(neil.parkwaycc.co.uk)
(The Firebird bug is bug 225669.)
Target Milestone: --- → mozilla1.6beta
Comment on attachment 135465 [details] [diff] [review]
Sort the theme names in the View/Apply and preferences windows

>-          <menupopup id="theme" datasources="rdf:chrome" ref="urn:mozilla:skin:root" oncommand="applyTheme(event.target)" onpopupshowing="checkTheme()">
>+          <menupopup id="theme" datasources="rdf:chrome" ref="urn:mozilla:skin:root" oncommand="applyTheme(event.target)" onpopupshowing="checkTheme()"
>+                     sortResource="http://www.mozilla.org/rdf/chrome#displayName"
>+                     sortDirection="ascending">
Although you were wise enough not to tack your attributes onto the end of this
overlong line it would have been nice if you could have rewrapped the line
while you were editing it ;-)
Attachment #135465 - Flags: review?(neil.parkwaycc.co.uk) → review+
Comment on attachment 135465 [details] [diff] [review]
Sort the theme names in the View/Apply and preferences windows

sr=alecf
Attachment #135465 - Flags: superreview?(alecf) → superreview+
Should we ask for 1.5b approval on this? I imagine it's pretty low-risk.
Obviously I meant 1.6b, sorry for the spam.
Attachment #135465 - Flags: approval1.6b?
Comment on attachment 135465 [details] [diff] [review]
Sort the theme names in the View/Apply and preferences windows

a=asa (on behalf of drivers) for checkin to 1.6 beta.
Attachment #135465 - Flags: approval1.6b? → approval1.6b+
patch checked in
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: