Yeah, it's most likely a similar issue; The addon isn't playing well with a restrictive CSP. What gesture addon are you specifically using, @the_funky_buddha? If you let me know which one it is, I...
Yeah, it's most likely a similar issue; The addon isn't playing well with a restrictive CSP. What gesture addon are you specifically using, @the_funky_buddha? If you let me know which one it is, I can look into opening an issue related to this on that addon's github/gitlab (if they have one) so the devs can be made aware of the problem.
It seems the dev is already aware of the addon's various CSP issues but unfortunately it looks like they have no intention of addressing it. :( See:...
It seems that the extension is writing directly to the page, so I'm surprised you haven't seen something like this before. It's more their fault than that of the page it's being used on. They...
It seems that the extension is writing directly to the page, so I'm surprised you haven't seen something like this before. It's more their fault than that of the page it's being used on.
They could at least be using an absolute div to bring it out of the document flow.
Yeah, it's most likely a similar issue; The addon isn't playing well with a restrictive CSP. What gesture addon are you specifically using, @the_funky_buddha? If you let me know which one it is, I can look into opening an issue related to this on that addon's github/gitlab (if they have one) so the devs can be made aware of the problem.
It's FoxyGestures. And thanks, that'd be much appreciated. The addon's been mostly flawless for me other than this.
It seems the dev is already aware of the addon's various CSP issues but unfortunately it looks like they have no intention of addressing it. :( See:
https://github.com/marklieberman/foxygestures/issues/230
https://github.com/marklieberman/foxygestures/issues/283
That sucks. And Gesturefy doesn't fully work with resistfingerprinting enabled either. Thanks.
Is this due to the site or my gesture addon in Firefox? I've been using this addon for many years and never encountered this issue on any other site.
It seems that the extension is writing directly to the page, so I'm surprised you haven't seen something like this before. It's more their fault than that of the page it's being used on.
They could at least be using an absolute div to bring it out of the document flow.