InformAction Forums

Thank you

I raised an issue: (1478037) Allow bookmarklets to run even when the CSP on the page would normally block javascript: execution · Issue #1512 · MrAlex94/Waterfox

Thanks

With apologies for a late response (I must have overlooked an e-mail notification):

barbaz wrote: ↑

Tue Jan 07, 2020 1:42 am

Not a reasonable assumption.

I struck through that part of my answer in Stack Exchange.

For example, the first bookmarklet at JavaScript Tricks: Edit Websites in Browser (Live) The behaviour of Waterfox Current 2020.03 is – as expected – consistent with the behaviour of Firefox ESR 68.6.0esr (64-bit): for an untrusted site, the bookmarklet does not work. With NoScript 11.0.23 added to ...

Thanks, was my response reasonable?

A January 2013 answer in Information Security Stack Exchange , part of which was quoted in a November 2019 question : Take into consideration that NoScript will also increase the attack surface My response: https://security.stackexchange.com/a/223723/13575 – the second part of the answer (below the ...

storage.googleapis.com

Excellent. Thanks for the explanation!

Now I need to discover what causes losses – https://discourse.mozilla.org/t/-/51431 ... ahamperrin

With a different profile, testing NoScript alone, I find prevention of registration but not loss of registered service workers. Screen recording: https://s.put.re/Nyu3Ek5J.mp4 If there's a way for NoScript to allow registration , this will be a step towards helping me to identify what may be partly ...

NoScript 11.0.11 with Firefox 72.0: service workers are lost, I see no way to prevent the loss.

Please, is this a known issue?

Background (before I identified NoScript as a cause): Absence of service workers in Firefox 72 : firefox

Road Trip – https://roadtrip.glitch.me/ When googletagmanager.com is blocked, there's no hint of the block in the main icon: https://s.put.re/yWd54iaJ.com.png Is this expected? NoScript 11.0.11 with Firefox 72.0: no hint. NoScript 5.1.9 with home-built Waterfox Classic 2019.12 (20200103060435): work...

Cross reference: Compiling Waterfox with clang causes extension conflict that crashes tabs · Issue #875 · MrAlex94/Waterfox

barbaz wrote: ↑

Fri Oct 19, 2018 8:24 pm

… status of TLS 1.3 support in Waterfox. It's at least not enabled by default.

(FWIW Waterfox about:support says it uses NSS version 3.32.1) …

Hi, FYI https://github.com/MrAlex94/Waterfox/is ... -449894974