@adeline
Search the Brave Community for tips . . . using terms:
video, D3D11, Metal, NVIDIA, Angle Graphics, OpenGL, Vulkan, WebGL, Skia Graphite (skia-graphite)
And search, using those terms, in a Brave Browser New Window at brave://flags - where you may experiment.
Test those graphics switches, with both conditions:
- Graphic Acceleration Enabled
- Graphic Acceleration Disabled
Note: IF Graphics Acceleration is Disabled, THEN websites might “think” that WebGL is OFF, when WebGL is still ON but not comprehended by the website ← see:
“Need help understanding and preventing fingerprinting” ← There, notice the details for the line: "Unmasked Renderer . . . " in each of the 2 screenshots:
With Graphics Acceleration OFF / DISABLED, the "Unmasked Renderer . . . " line reads: “ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)”
With Graphics Acceleration ON / ENABLED, the "Unmasked Renderer . . . " line reads: “ANGLE (Google, NVIDIA, NVIDIA GeForce RTX 3080 (0x00002206) Direct3D11 vs_5_0 ps_5_0, D3D11)”
Some websites see the “ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)” . . . and do not “get it” (that WebGL is actually enabled).
Those websites may, or may not, display a pop-up window that prompts the visitor: “Please enable WebGL”
If the website does not “get it” (that WebGL is actually enabled), but the webites does not display a pop-up window for the visitor ← THEN the Brave Browser user might spend a lot of time, fiddling around with Brave Shields settings, throwing various switches, disabling a variety of extensions, and re-installing Brave Browser, etc., while trying to find a fix.