You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-21Lines changed: 0 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,27 +11,6 @@ as per domain name.
11
11
Available on Chrome web store (<ahref="https://chrome.google.com/webstore/detail/httpswitchboard/mghdpehejfekicfjcdbfofhcmnjhgaag">HTTP Switchboard</a>),
12
12
or you can [install manually](https://github.com/gorhill/httpswitchboard/tree/master/dist).
13
13
14
-
###IMPORTANT
15
-
16
-
Because of [issue #35](https://github.com/gorhill/httpswitchboard/issues/35), it is best to disable javascript by default. To do so:
17
-
18
-
- Go to chrome/chromium *Settings*.
19
-
- You might need to click *Show advanced settings*.
20
-
- In *Privacy* section, click *Content settings...* button.
21
-
- In the *Javascript* section, click "Do not allow any site to run JavaScript".
22
-
23
-
HTTP Switchboard will continue to disable/enable javascript just as before, according to whether
24
-
the hostname is black or whitelisted, except that now, since javascript is turned off by default,
25
-
there is no opportunity for inline scripts to be executed before the asynchronous command
26
-
([as per chromium API](http://developer.chrome.com/extensions/overview.html#sync)) to disable them takes effect.
27
-
28
-
Sadly, a side-effect of doing the above steps is that it may happen that inline scripts are not
29
-
executed the first time you visit a site for which scripts are whitelisted. Forcing a reload of the
30
-
page fix this.
31
-
32
-
The only way to resolve this annoyance is for [chromium developers to
33
-
come up with a solution](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/AOAlQyQmbBI).
0 commit comments