uBlock/platform/chromium
Raymond Hill eed13194fb
Handle possible exceptions in vAPI.messaging.broadcast()
I had exceptions thrown by that code once in a while,
about the `port` object not being connected; possibly
occurs only when using dev tools with breakpoints
in uBO's code. Even if this can be reproduced randomly
only when debugging uBO, it costs nothing to add code
in there to handle exceptions.
2019-05-21 14:07:38 -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 fix reported extension error in Chrome 72.0.3622.0 2018-12-05 14:46:35 -05:00
vapi-background.js Handle possible exceptions in vAPI.messaging.broadcast() 2019-05-21 14:07:38 -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 Refactor selfie generation into a more flexible persistence mechanism 2019-02-14 13:33:55 -05: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 Add ability to report exception cosmetic filters in the logger 2019-05-16 13:44:49 -04:00
vapi-usercss.real.js Fix regression in applying procedural cosmetic filters 2019-05-16 17:22:20 -04:00
vapi-webrequest.js Make use of `X-DNS-Prefetch-Control` in Chromium-based browsers 2019-04-27 13:12:33 -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