Previously, "block scripts" filtered requests at the network level by content type, which meant inline scripts weren't being blocked. This sets javascript: false on the webContents, which truly disables all JS.
We still need JS for the browser internal pages (settings/reader/PDF viewer), so this checks the URL on each navigation and re-creates the view with an updated preference value if necessary.
Previously, "block scripts" filtered requests at the network level by content type, which meant inline scripts weren't being blocked. This sets
javascript: falseon the webContents, which truly disables all JS.We still need JS for the browser internal pages (settings/reader/PDF viewer), so this checks the URL on each navigation and re-creates the view with an updated preference value if necessary.
Fixes #2382.