forked from mirrors/gecko-dev
Bug 1855151 has some example of confusion this causes, and bug 221490 has some more history. I don't see why chrome://foo/content should be different from chrome://foo/skin etc, in terms of privileges. I guess in the past this distinction probably made more sense? Per discussion in the review comments, we're not touching langpacks (yet). Differential Revision: https://phabricator.services.mozilla.com/D189232 |
||
|---|---|---|
| .. | ||
| test | ||
| moz.build | ||
| nsChromeProtocolHandler.cpp | ||
| nsChromeProtocolHandler.h | ||
| nsChromeRegistry.cpp | ||
| nsChromeRegistry.h | ||
| nsChromeRegistryChrome.cpp | ||
| nsChromeRegistryChrome.h | ||
| nsChromeRegistryContent.cpp | ||
| nsChromeRegistryContent.h | ||
| nsIChromeRegistry.idl | ||
| nsIToolkitChromeRegistry.idl | ||
| RegistryMessageUtils.h | ||