Toolkit:Platform Specific Extension Components: Difference between revisions

Toolkit:Platform Specific Extension Components (view source)

336 bytes added , 23 May 2005

Confirmed users, Bureaucrats and Sysops emeriti

1,217

edits

@@ Line 79: / Line 79: @@
               mycomponent.dll
-== Open Issues ==
+== Resolved Issues ==
-* What happens when we put chrome jar files in the platform directories - do they have to be listed in the main chrome.manifest? What if the current platform doesn't have that file, is it just ignored?
+<dl>
-* What happens to preference files - what happens if two have the same name, in which sequence are they loaded, are prefs overwritten if specified in both the base prefs file and a platform-specific one?
+<dt>What happens when we put chrome jar files in the platform directories - do they have to be listed in the main chrome.manifest? What if the current platform doesn't have that file, is it just ignored?
+<dd> Each platform directory may have its own chrome.manifest:
+<pre>chrome.manifest
+platform/WINNT/chrome.manifest
+platform/WINNT_msvc/chrome.manifest</pre>
+<dt>What happens to preference files - what happens if two have the same name, in which sequence are they loaded, are prefs overwritten if specified in both the base prefs file and a platform-specific one?
+<dd> Yes, we should read the "base" preferences first, then the platform-specific ones, and the pref system will automatically override any duplicate prefs.
+</dl>
 == Bug References ==