Search completed in 1.23 seconds.
nsIContentPolicy - Archive of obsolete content
dom/base/
nsicontentpolicy.idlscriptable interface used to implement a content policy mechanism.
... 63 introduced gecko 1.0 inherits from:
nsicontentpolicybase last changed in gecko 42 (firefox 42 / thunderbird 42 / seamonkey 2.39) you can observe content that is being loaded into your browser by implementing
nsicontentpolicy.
... warning: do not block the caller in your implementations of shouldload() or shouldprocess() (for example, by launching a dialog to prompt the user for something).") note: in reality, much of this interface is defined in the
nsicontentpolicybase interface, but for now is documented here until someone has time to split things up.
...And 4 more matches
Finishing the Component
the interface that we need for this project is something called
nsicontentpolicy.
...(for weblock, all you need are the headers for
nsicontentpolicy and the
nsicontentpolicy.idl.) then, using the same steps you used to create the weblock.h, create a header from this idl file using the xpidl compiler.
... once you have these interface and header files, you can modify the weblock class to implement the
nsicontentpolicy interface.
...And 11 more matches
Intercepting Page Loads - Archive of obsolete content
content policy finally, there is the option of implementing
nsicontentpolicy.
... you can create an xpcom component that extends
nsicontentpolicy and register it to the "content-policy" category using the nsicategorymanager.
... the
nsicontentpolicy.shouldload() method is the only one in this interface that is really useful.
...And 2 more matches
Limitations of chrome scripts
nsicontentpolicy without the shim in multiprocess firefox, if you register the
nsicontentpolicy in the chrome process then it will never see any attempts to load web content, because they happen in the content process.
...it transparently registers an
nsicontentpolicy in the content process, whose shouldload just forwards to the chrome process.
... to make the shim unnecessary: define and register
nsicontentpolicy in the content process.
nsIIOService
any of the content types defined in
nsicontentpolicybase.idl.
...any of the content types defined in
nsicontentpolicy.idl return value an nsichannel for the uri.
...any of the content types defined in
nsicontentpolicy.
Performance
} object.assign(contentypolicy.prototype, { classdescription: ..., classid: ..., contractid: ..., queryinterface: xpcomutils.generateqi([ci.
nsicontentpolicy]), shouldload: function(type, location, origin, context) { let resultlist = services.cpmm.sendsyncmessage("my-addon:check-load", {destination: location, source: origin}) // <=== sync message!
... if(resultlist.every((r) => r == true)) return ci.
nsicontentpolicy.accept; return ci.
nsicontentpolicy.reject_request; } }); // more boilerplate code here this example is a (somewhat condensed) content policy which gets triggered for every network request in a child process to either allow or deny the request.
XPCOM Objects - Archive of obsolete content
cc[@mozilla.org/categorymanager;1].getservice(ci.nsicategorymanager); acompmgr.queryinterface(ci.nsicomponentregistrar); acompmgr.registerfactorylocation( class_id, class_name, contract_id, alocation, aloaderstr, atype); categorymanager.addcategoryentry( "content-policy", "xulschool hello world", contract_id, true, true); }, in this case the component would need to implement
nsicontentpolicy.
Index - Archive of obsolete content
1997 mozilla.dev.platform faq faq for questions asked on mozilla.dev.platform 1998
nsicontentpolicy interfaces, interfaces:scriptable, needsmarkupwork, reference, xpcom, xpcom interface reference you can observe content that is being loaded into your browser by implementing
nsicontentpolicy.
Installing headers using EXPORTS
here is an example <tt>makefile.in</tt> which has both c++ and idl headers: module = content xpidl_module = content_base exports = \ nsicontent.h \ nsidocument.h \ nsistylesheet.h \ $(null) xpidlsrcs = \
nsicontentpolicy.idl \ nsiselectioncontroller.idl \ $(null) include $(topsrcdir)/config/rules.mk ...
Process scripts
for example, in multiprocess firefox, if you need to use
nsicontentpolicy to register a content policy, you must do this in the content process.
WebRequest.jsm
you can use this api to implement a content policy in an add-on (for example, an ad or script blocker), as you could using
nsicontentpolicy.
Preface
finish implementing the weblock component:
nsicontentpolicy, file i/o, locking, etc.
Creating XPCOM components
ory service modifying paths with nsifile manipulating files with nsifile using nsilocalfile for reading data processing the white list data iweblock method by method lock and unlock addsite removesite setsites getnext getsites hasmoreelements finishing the component using frozen interfaces copying interfaces into your build environment implementing the
nsicontentpolicy interface receiving notifications implementing the
nsicontentpolicy uniform resource locators checking the white list creating nsiuri objects building the weblock ui user interface package list client code overview xul the xul document the locking ui site adding ui weblock.xul overlaying new user interface into mozilla weblockoverlay.xul other res...
nsIChannelPolicy
loadtype unsigned long indicates what type of content is being loaded, for example
nsicontentpolicy::type_image.
XPCOM Interface Reference by grouping
nsiinprocesscontentframemessagemanager nsiscriptableio nsixpcscriptable future nsixmlhttprequestupload obsolete nsixmlrpcclient nsixmlrpcfault security auth nsiauthmodule nsiauthprompt nsiauthpromptprovider nsiauthpromptwrapper nsiasyncverifyredirectcallback content
nsicontentpolicy credentials nsilogininfo nsiloginmanager using nsiloginmanager nsiloginmanagerstorage nsiloginmetainfo history nsiglobalhistory nsiglobalhistory2 nsiglobalhistory3 ssl nsibadcertlistener2 system action nsicancelable ...