Closed Bug 59091 Opened 24 years ago Closed 13 years ago

chrome://foo.gif urls hardcoded in c++ source [tracking bug]

Categories

(Core Graveyard :: Skinability, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Keywords: helpwanted, meta)

This is a tracking bug to track all instances of chrome:// urls to GIF files
that are hardcoded in c++ source.  This can be closed once all the bugs it
depends on are closed.
Depends on: 59092, 59093
Until all the bugs blocking this one are fixed, it will not be possible to 
create a skin using only PNGs (or MNGs for that matter). This therefore blocks
bug 8415.
Blocks: 8415
Keywords: meta
Depends on: 59094, 59095, 59096, 59097, 59098, 59099
A comment:

the common dialog service allows clients to specify the image to be displayed in
the dialog. 9 times out of 10, this is one of four standard images, /HOWEVER/
sometimes the client can provide their own image (e.g. the drag-link-home
alert). So getting rid of hardcoded URLs breaks down here, because the client
(in this case, navigator) has no way of creating a rule to be matched in the
common dialog code (which lives in global).

Thoughts? 
Ben, the complaint here is not that hard-coded URLs are included at all, it is 
that we are effectively insisting that skin authors use the GIF format for them.

> 9 times out of 10, this is one of four standard images

Er, three standard images and one non-standard image, actually. See bug 59820.
QA Contact: blakeross → pmac
Mass move skinability bugs to nobody@mozilla.org, helpwanted. 
Assignee: ben → nobody
Keywords: helpwanted
Filter on "Nobody_NScomTLD_20080620"
QA Contact: pmac → skinability
Product: Core → Core Graveyard
Closing as per original description.  All dependent bugs are closed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.