Closed Bug 59093 Opened 24 years ago Closed 23 years ago

Hardcoded chrome URL to a GIF file in extensions/cookie/nsCookie.cpp

Categories

(Core Graveyard :: Skinability, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Keywords: helpwanted)

In extensions/cookie/nsCookie.cpp, there are two instances of harcoded chrome:// urls to GIF files: nsString tempStr; tempStr.AssignWithConversion("chrome://global/skin/question-icon.gif"); and nsString("chrome://global/skin/question-icon.gif").GetUnicode() These should not be hardcoded.
Blocks: 59091
Pretriage of skinnability bugs, marking nsbeta1-. The real question is how to allow people to load up an icon using common dialog services without referencing a filename. Certainly not going to get fixed for beta1.
Keywords: nsbeta1-
Marking nsbeta1- bugs as future to get off the radar
Target Milestone: --- → Future
QA Contact: blakeross → pmac
Mass move skinability bugs to nobody@mozilla.org, helpwanted.
Assignee: ben → nobody
Keywords: helpwanted
The hardcoded chrome referenced in this bug report is no longer present in nsCookie.cpp. It was removed by morse@netscape.com in version 1.105 of the file. One step closer to clearing the blockers for bug 59091 and eventually bug 8415.
marking fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.