Bug: Whitelist ignores WebGL filter option

[Jorgo]

Hello,

I have activated all options under the "Embeddings" tab except to "Apply these restrictions to whitelisted sites too". I have a blog based on the TYPO3 CMS, which I have whitelisted in NoScript. When logging into my CMS backend, NoScript tells me it has blocked WebGL options which I can then temporarily enable. This should not be happening with the above combination of options, IMHO. I have tried whitelisting with short domain, full domain and qualified URL, all with the same result. Thanks for looking into it!

Best,
Jorgo

[therube]

I believe anything listed below "Apply these restrictions to whitelisted sites too" is going to act globally if enabled?

[Giorgio Maone]

I believe anything listed below "Apply these restrictions to whitelisted sites too" is going to act globally if enabled?

Correct.

[Jorgo]

I see. Maybe it could be made a bit clearer by grouping these options somehow visually.

[Giorgio Maone]

I see. Maybe it could be made a bit clearer by grouping these options somehow visually.

Actually, to be more precise, "Forbid WebGL" is not listed above because it does make sense only if JavaScript is enabled. In facts, you can create a 3D (WebGL) canvas only through JavaScript, therefore this option is meaningful on whitelisted sites only.

[Thrawn]

Is there a preference in about:config to specify exceptions for this?

[Giorgio Maone]

Is there a preference in about:config to specify exceptions for this?

Please check latest development build 2.6.6.6rc1, thanks.