Closed Bug 226603 Opened 21 years ago Closed 11 years ago

Firefox Application, Window and Document Icons

Categories

(Firefox :: General, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bugs, Unassigned)

References

Details

(Keywords: conversion, meta)

This bug tracks all system icon requirements for Firebird for 1.0, three categories:

- application (used to start the app)
- document (documents we can open)
- window (Windows only, used for the title bar of specific application windows)

All of these icons must share the same visual theme, rather than a hodge podge,
and must adapt properly to different OSes (e.g. Mac icons are high quality, use
same motifs/styles as windows ones but look more detailed/aqua)
.
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → Firebird1.0
Keywords: conversion
*** Bug 214054 has been marked as a duplicate of this bug. ***
sigh.
Summary: Firebird Application, Window and Document Icons → Firefox Application, Window and Document Icons
Flags: blocking0.9?
Depends on: docicons
Target Milestone: Firefox1.0 → Firefox1.0beta
target is 1.0beta, not a blocker for 0.9
Flags: blocking0.9? → blocking0.9-
QA Contact: mconnor
Flags: blocking1.0?
Depends on: 242050
Flags: blocking1.0? → blocking1.0+
Given that there will actually be seperate document icons for files associated
with Firefox, shouldn't there be something in options (in Windows, at least)
that allows you to check which files you do and don't want associated with
Firefox?  I recently had to manually associate .swf with Firefox, and it was a
PITA.  Windows' automatic association doesn't work too well - to do it properly
(ie. get the Firefox icon associated with the filetype), I had to go into
advanced settings, which I can't see the average user doing.  It's also worth
noting that most Windows apps that do associate with certain files have this
type of in-app dialog box - it's the standard Windows way of doing things (see
Paint Shop Pro, Photoshop, Winamp, Winzip, WinRAR, WinACE, Cool Edit... plenty
more).

I know that you've marked that feature as WONTFIX, Ben, but I think you ought to
reconsider.  It's not a very good idea to grab a set of default extensions if
you're not going to give the user the option to then deselect some of them if
they would rather Firefox not auto-associate with them, or to select additional
filetypes they would like to associate Firefox with (ie. SWF).
Severity: critical → minor
Priority: P1 → P3
Severity: minor → normal
Priority: P3 → P2
Flags: blocking-aviary1.0RC1+
Assignee: bugs → sspitzer
Status: ASSIGNED → NEW
Flags: blocking-aviary1.0RC1+ → blocking-aviary1.0RC1-
Flags: blocking0.9-
No longer a "blocker"
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
Assignee: sspitzer → nobody
Keywords: meta
QA Contact: mconnor → general
Target Milestone: Firefox1.0beta → ---
Shouldn't this bug me changed to RESOLVED or EXPIRED?
no longer relevant
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.