Closed Bug 199576 Opened 19 years ago Closed 12 years ago

Icons should have consistent names.

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: netdragon, Assigned: jag+mozilla)

References

Details

This is a development issue. There is no consistancy between the names of the 
icons. They follow three patterns:

XXXX-window.ico
XXXXWindow.ico
XXXX.ico


contents of mozilla/xpfe/bootstrap/icons/windows:
 chatzilla-window.ico
 history-window.ico
 abcardWindow.ico
 downloadManager.ico
 jsconsoleWindow.ico
 addressbookWindow.ico
 editorWindow.ico
 main-window.ico
 venkman-window.ico
 bmPropsWindow.ico
 findBookmarkWindow.ico
 messengerWindow.ico
 winInspectorMain.ico
 bookmark-window.ico
 findHistoryWindow.ico
 mozilla.ico
 calendar-window.ico
 msgcomposeWindow.ico

Different issue: Maybe they should also be sorted into various subdirectories 
based on what portion of Mozilla they are associated with.
the magic comes from
<window id="prefixto">

"prefixto" ## ".ico"

you'd have to get approval from each module owner to make the change...
Blocks: icons
Perhaps it shouldn't be hardcoded like that and should have an intermediary
translation to the icon name.
Product: Core → Mozilla Application Suite
Summary: Icons should have consistant names. → Icons should have consistent names.
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.