зеркало из https://github.com/mozilla/gecko-dev.git
edd6809d0c
Some extensions want to implement about: pages and we want those pages to be loaded in the extension process, not in the web content process, so that: 1) a compromised web process won't get access to the about: page content 2) the extension page can use all the APIs that extension pages normally get, instead of only content script APIs. Post-Fission we will need to know which extension process to choose. Differential Revision: https://phabricator.services.mozilla.com/D24989 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
moz.build | ||
nsAboutBlank.cpp | ||
nsAboutBlank.h | ||
nsAboutCache.cpp | ||
nsAboutCache.h | ||
nsAboutCacheEntry.cpp | ||
nsAboutCacheEntry.h | ||
nsAboutProtocolHandler.cpp | ||
nsAboutProtocolHandler.h | ||
nsAboutProtocolUtils.h | ||
nsIAboutModule.idl |