Skip to content
This repository was archived by the owner on Nov 15, 2017. It is now read-only.

Why does HTTPSB allow all javascript in Chromium settings?!?

Jump to bottom
Raymond Hill edited this page Jan 3, 2014 · 13 revisions

When HTTP Switchboard is installed and active, if you look at Chromium Settings/Privacy/Content settings/Javascript/Manage exceptions, you will notice two entries (created by HTTPSB):

  • http://* allow
  • https://* allow

Do not panic.

HTTPSB uses a different and more reliable mechanism than other blockers on the Chromium platform to enforce the blocking of javascript. There are two ways in which javascript must be blocked:

  • Inline javascript
  • External javascript

For external javascript, this is trivial with the Chromium platform using the webRequest API to prevent the downloading of javascript files.

For inline javascript however, it is a bit more complicated.

Usually javascript blockers on the Chromium platform use (or try to) the contentSettings API, but this has proven challenging as the calls to create/delete rules in order to block javascript are not synchronous, meaning they take effect at some point in the future. This is problematic when it comes to block inline javascript.

Clone this wiki locally