After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 776522 - Option to disable Javascript
Option to disable Javascript
Status: RESOLVED DUPLICATE of bug 400525
Product: epiphany
Classification: Core
Component: Preferences
3.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-27 14:24 UTC by ominous
Modified: 2017-07-07 19:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ominous 2016-12-27 14:24:00 UTC 
Please introduce an option to disable Javascript. On my ultrabook certain Javascript bloated websites can cause bad hick ups and freezes.

I do not require Javascript to read web pages so I rather want to have it disabled.
Comment 1 Michael Catanzaro 2016-12-27 15:46:45 UTC 
This option was removed recently after I noticed that the overview and the unacceptable TLS certificate error page were broken with JavaScript disabled. Fact is Epiphany needs JavaScript for its own pages, so we need to exempt Epiphany's own pages from that, but that requires a bit of work. And disabling JavaScript globally is going to break tons of websites, so we really need a way to add exceptions, similar to NoScript. I think bug #400525 covers this issue nicely, so I'll mark this as a duplicate.

*** This bug has been marked as a duplicate of bug 400525 ***
Comment 2 Michael Catanzaro 2016-12-27 15:47:44 UTC 
To be clear: I don't want to bring back a global disable JavaScript option unless we also have some mechanism for adding exceptions.
Comment 3 Dan Jacobson 2017-07-07 17:45:16 UTC 
A simple on/off toggle should be available. More fancy stuff could be added later.
Comment 4 André Klapper 2017-07-07 17:56:44 UTC 
No. Please do read previous comments before commenting.
Comment 5 Dan Jacobson 2017-07-07 18:02:45 UTC 
Yes, internally you would whitelist yourself. Externally, the user would just see
[✓] Disable scripts
Comment 6 André Klapper 2017-07-07 18:05:12 UTC 
Dan, this task is closed as a duplicate. Please stop commenting here.
Comment 7 Michael Catanzaro 2017-07-07 19:33:15 UTC 
(In reply to Dan Jacobson from comment #5)
> Yes, internally you would whitelist yourself.

This is not currently possible. We will need to take the time to build out a real NoScript feature, bug #400525. Then a whitelist approach would be possible.