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

Status: RESOLVED INVALID

(Core :: XUL, defect)

Description

[Simon Fraser [no longer active]]

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.

Comment 1

[Simon Fraser [no longer active]]

Attachment: An installed-chrome.txt which causes problems now

Comment 2

[Peter Trudelle]

worked around with build scripts, yes? (Future).

Comment 3

[Simon Paquet [:sipaq]]

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".

Comment 4

[Simon Paquet [:sipaq]]

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.