chrome registry is sensitive to ordering in installed-chrome.txt

RESOLVED INVALID

Status

()

Core
XUL
RESOLVED INVALID
18 years ago
10 years ago

People

(Reporter: Simon Fraser, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

18 years ago
Currently, there are ordering dependencies in with installed-chome.txt such that 
skin packages registered after the skin 'select' use a 'default' skin. This is 
causing some of the AIM CSS files in Mac developer builds to come from the modern 
skin, even when using classic.

Talking to hyatt, we decided that chrome registration should store and process 
'select' lines only after all the other packages have been registered.
(Reporter)

Comment 1

18 years ago
Created attachment 16289 [details]
An installed-chrome.txt which causes problems now

Comment 2

18 years ago
worked around with build scripts, yes? (Future).
Target Milestone: --- → Future

Comment 3

15 years ago
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
(Reporter)

Updated

15 years ago
OS: Mac System 8.5 → All
Hardware: Macintosh → All

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets

Comment 4

10 years ago
This bug hasen't been touched for years and is clearly unowned. Moving back to default assignee/QA so that people, who are watching those can accurately triage this bug.

Also resetting Priority, Target Milestone, Status Whiteboard and Status.
Assignee: hyatt → nobody
Priority: P3 → --
Target Milestone: Future → ---

Updated

10 years ago
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.