Bug #286


Bugs when leaving a JavaScript enabled page for one that isn't

Added by Soren Stoutner about 6 years ago. Updated over 5 years ago.

Start date:
Due date:
% Done:


Estimated time:


For example, if JavaScript is enabled in domain settings for DuckDuckGo, but not for the next site, a bunch of code is displayed when JavaScript is disabled before the new site loads.

Also, when leaving a Wordpress site, like, if JavaScript is disabled, it reloads the site instead of going to the new URL. Examples can bee seen at


DuckDuckGo Corruption.png (254 KB) DuckDuckGo Corruption.png Soren Stoutner, 05/25/2018 02:00 PM
Actions #1

Updated by Soren Stoutner about 6 years ago

  • Tracker changed from Feature to Bug
Actions #3

Updated by Soren Stoutner about 6 years ago

  • Status changed from Closed to In Progress

It turns out this fix doesn't handle all circumstances. For example, clicking Google Play from (doesn't load the first time) or loading from the home page (corruption on DuckDuckGo).

Actions #4

Updated by Soren Stoutner about 6 years ago

The problem with corruption of DuckDuckGo only happens the first time a particular website is loaded from it. If the user goes back and loads it again, the problem doesn't appear (likely some information it is waiting for is now cached and so there isn't enough time to corrupt the DuckDuckGo site).

Actions #5

Updated by Soren Stoutner almost 6 years ago

  • Status changed from In Progress to New
  • Priority changed from Next Release to 4.x

These are two separate but related problems. Both of them relate to having custom Domain Settings for particular URLs.

1. The issue with corruption on the DuckDuckGo homepage is caused because JavaScript is disabled by default but enabled for using Domain Settings. When JavaScript is disabled before loading the new URL it is applied to the current webpage, which causes display corruption.
2. The issue with loading Google Play from is caused because uses the default User Agent (PrivacyBrowser/1.0) while Google Play uses a custom User Agent (WebView Default). When the new user agent is applied it reloads the current webpage.

After playing around with `WebView.onPause()` and `WebView.pauseTimers()` in various locations, it seems to me that there is no way to fix this bug until Privacy WebView is released as part of the 4.x series.


Also available in: Atom PDF