uBlock/platform/chromium
Raymond Hill ca9b29c7ec
Distinguish between priviledge and unprivileged messages
Related issue:
- https://github.com/uBlockOrigin/uBlock-issues/issues/710

Messages from unprivileged ports (i.e. from content scripts)
are no longer relayed to message handlers which are to be
strictly used to execute privileged code.

The last remaining case of unprivileged messages which
should be converted into a privileged ones will be taken
care of when the following issue is fixed:
- https://github.com/gorhill/uBlock/issues/3497
2019-09-01 12:43:12 -04:00
..
is-webrtc-supported.html fix warnings in browser console 2017-07-25 11:59:52 -04:00
is-webrtc-supported.js this fixes https://github.com/gorhill/uBlock/issues/533#issuecomment-167931681 2015-12-31 09:24:55 -05:00
managed_storage.json #985: might be the missing trailing `#` 2015-11-27 14:30:17 -05:00
manifest.json Add virtuous signal that remote code execution is not possible 2019-07-21 10:37:58 -04:00
vapi-background.js Distinguish between priviledge and unprivileged messages 2019-09-01 12:43:12 -04:00
vapi-client.js Minor generic code review of changes since 1.18.2 2019-02-02 08:09:34 -05:00
vapi-common.js Distinguish between priviledge and unprivileged messages 2019-09-01 12:43:12 -04:00
vapi-usercss.js Add ability to report exception cosmetic filters in the logger 2019-05-16 13:44:49 -04:00
vapi-usercss.pseudo.js Fix internal cosmetic filter being reported in the logger 2019-06-20 07:14:34 -04:00
vapi-usercss.real.js Fix internal cosmetic filter being reported in the logger 2019-06-20 07:14:34 -04:00
vapi-webrequest.js Add ability to suspend network request handler at will 2019-06-30 10:09:27 -04:00
vapi.js refactor some webRequest-related code (now that firefox legacy is out of the way) 2018-10-28 10:58:25 -03:00