
Hello Vincent,
Thank you for your question and for reaching out with your question today.
It appears that you have identified a bug in Microsoft Edge (Chromium-based) and possibly Chromium itself regarding the rendering of WebGL programs on Windows 11 with AMD Radeon Graphics. You have also found a workaround by manually setting the graphics backend to D3D11onD12, which resolves the glitchy effect.
While I can understand your frustration, as an AI language model, I don't have direct contact with the developers of Edge or Chromium. However, I can suggest a couple of steps you can take to report this issue and potentially help the developers address it:
- Provide Feedback: Within Microsoft Edge, you can go to the "..." menu in the top-right corner, select "Help and feedback," and then choose "Send feedback" to submit a bug report. Describe the issue, provide the steps to reproduce it, and include your system information. This feedback will be valuable for the Edge development team.
- Visit the Chromium Bug Tracker: Chromium has an issue tracker where you can search for existing bug reports or submit a new one. Visit the Chromium bug tracker website (**************************) and search for similar issues. If you don't find a matching report, you can create a new one with the details you've provided here.
When reporting the bug, include the following information:
- Detailed description of the issue, including the glitchy effect and the specific WebGL program that triggers it.
- Mention that the issue occurs on Windows 11 with AMD Radeon Graphics.
- Provide your GPU information, including the driver version and DirectX version.
- Mention the workaround you discovered by setting the graphics backend to D3D11onD12.
- Include any relevant screenshots or video recordings demonstrating the problem.
- Mention that the issue occurs in both Microsoft Edge and Chromium.
By reporting the issue through these channels, you can bring it to the attention of the respective development teams, who may be able to investigate and address the problem in future updates.
It's worth noting that software bugs can be complex, and the resolution time can vary. Patience and continued communication with the developers will be key in helping them understand and fix the issue.
In the meantime, if the workaround of setting the graphics backend to D3D11onD12 resolves the problem for you, you can continue using it as a temporary solution until the bug is addressed.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
If the reply was helpful, please don’t forget to upvote or accept as answer.