589430 - chrome.manifest is no longer read from chrome directory

Status: RESOLVED WONTFIX

(Toolkit Graveyard :: XULRunner, defect)

Description

[Georg Maaß]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.12pre) Gecko/20100812 Lightning/1.0b1 SeaMonkey/2.0.7pre
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b5pre) Gecko/20100818

Since somewhere in 2.0b4pre chrome.manifest is no longer read from chrome directory but only from directory where application.ini resides. Additional manifest files are not read at all.

Until the latest XulRunner nightly from 2.0b3pre chrome.manifest and all other manifest-files where read from chrome directory being a child directory of the directory where application.ini resides.

I I make the error console being the start window I get this info:

Could not read chrome manifest file '/Volumes/Test/gmL.app/Contents/Resources/chrome.manifest'.

This information is correct because the location of the chrome.manifest and other manifest files is: "/Volumes/Test/gmL.app/Contents/Resources/chrome/"

If I place the chrome.manifeste to the desired location it is found, but the other manifest files are not loaded independet of whether I place them at "/Volumes/Test/gmL.app/Contents/Resources/" or at their traditional location in "/Volumes/Test/gmL.app/Contents/Resources/chrome/".

As a result of this my application no longer finds anything even the start window of the application is not found, if I switch from XulRunner 2.0b3pre to XulRunner 2.0b4pre or newer.

Reproducible: Always

Comment 1

[Benjamin Smedberg]

This was an intentional change in behavior. Only the root chrome.manifest is read, and you can include other manifests from that one using the 'manifest' directive.