this post was submitted on 19 Jun 2024
19 points (91.3% liked)

Firefox

18050 readers
184 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 5 years ago
MODERATORS
 

Straight to the point: Is there some way to add a button or shortcut to quickly enable/disable WebGL without having to find it in settings every time?

The only issues I'm having using FF are all related to having WebGL disabled, so I find myself reactivating it relatively often. I wish there was some kind of quick way to enable it for this session only, or for this tab only. If you have any ideas, please let me know.

top 17 comments
sorted by: hot top controversial new old
[–] chaospatterns@lemmy.world 3 points 6 months ago (1 children)

NoScript enables you to enable or disable WebGL per site. If you don't want to deal with the hassle of websites being broken, you can set the default to enable JS but disable WebGL then set applications to be trusted with WebGL.

[–] Clandestine@lemmy.zip 2 points 6 months ago

I'll try this, thanks!

[–] Album@lemmy.ca 3 points 6 months ago (3 children)

Why do you disable it at all?

[–] Album@lemmy.ca 5 points 6 months ago (1 children)

Well I appreciate the downvote from ya but this is likely an x-y problem.

https://xyproblem.info/

Was going to suggest an extension to create false fingerprinting since I can't think of any other reason.

[–] Clandestine@lemmy.zip 3 points 6 months ago (1 children)

Yeah that's the other solution I was thinking of.

[–] Album@lemmy.ca 5 points 6 months ago* (last edited 6 months ago) (1 children)

Yes, exactly, that's what I use.

Instead of trying to solve the problem of Fingerprinting by completely disabling and then finding ways of enabling/disabling, you can solve the problem by just spoofing the fingerprinting.

Helps to present the problem first, instead of the solution you think is best but can't find an answer for. Usually the reason is that there is a better solution.

Test the implementation here: https://browserleaks.com/

[–] Clandestine@lemmy.zip 1 points 6 months ago (1 children)

Well asking the right question is also a skill, seems I'm still learning that one! Thank you

[–] Album@lemmy.ca 1 points 6 months ago

Agreed, cheers

[–] Clandestine@lemmy.zip 4 points 6 months ago

WebGL is a strong fingerprinting vector, and as it is not needed for 95% of the webpages I use, I'd rather keep it off. And since the last 5% is a bit annoying at times, I wanted to hear if there are good solutions out there.

[–] Cheradenine@sh.itjust.works 2 points 6 months ago (1 children)

Because it's a privacy and security risk? Because it reduces fingerprinting?

[–] Album@lemmy.ca 1 points 6 months ago (1 children)

But disabling it creates a whole slew of issues, hence the post. Turns out there's much better solutions.

[–] Cheradenine@sh.itjust.works 3 points 6 months ago (1 children)

What are the issues? Both my browsers have it disabled.

[–] Album@lemmy.ca 0 points 6 months ago* (last edited 6 months ago) (1 children)

Oh yeah i forgot your use cases are the same as everyone else's.

OP has the issues. ask them.

[–] Cheradenine@sh.itjust.works 3 points 6 months ago (1 children)

OP did not elaborate on their issues. You said it creates a whole slew of issues, I asked what they were.

No need for a strawman here. What are the issues?

[–] Clandestine@lemmy.zip 2 points 6 months ago

I've had exactly two issues that have actually affected me.

1: The screen sharing didn't show up in Zoom, when watching a lecture.

2: When looking for an apartment to rent, the integrated map on the site didn't show. Which was very unpractical as I couldn't see the location of the flat I was looking at.

Haven't had any other problems, so I wouldn't call this a slew of problems either. Both problems were solved by enabling WebGL and refreshing.

[–] possiblylinux127@lemmy.zip 2 points 6 months ago (1 children)

On librewolf I get a popup when a site wants to use openGL

[–] Clandestine@lemmy.zip 1 points 6 months ago

What I'm using LibreWolf and I didn't. I probably disabled it at some point then. Oops