Avoid Firefox/macOS WebGPU shader failure by falling back to WebGL#191
Draft
Copilot wants to merge 2 commits into
Draft
Avoid Firefox/macOS WebGPU shader failure by falling back to WebGL#191Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Agent-Logs-Url: https://github.com/TUDA-MUST/ITEP/sessions/b9f16c47-76fa-4da5-8afa-43c9ff06a124 Co-authored-by: axeljaeger <2556899+axeljaeger@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix shader error in Firefox on Mac
Avoid Firefox/macOS WebGPU shader failure by falling back to WebGL
May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Firefox 146 on macOS can fail WebGPU pipeline compilation (
Metal ... redefinition of '_tmp'), leaving the 3D canvas white. This change avoids that browser/OS-specific failure by selecting a safe rendering backend at engine init time.Engine selection hardening
shouldUseWebGPUEngine(userAgent, platform)inbabylon-jsview.directive.ts.initEnginenow uses:Engine) specifically for Firefox on macOS.WebGPUEngine | Engine | NullEngine).Targeted compatibility coverage
babylon-jsview.directive.spec.tswith explicit assertions for:Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
fonts.googleapis.com/home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell --disable-field-trial-config --disable-REDACTED-networking --disable-REDACTED-timer-throttling --disable-REDACTEDing-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-REDACTED-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AvoidUnnecessaryBeforeUnloadCheckSync,BoundaryEventDispatchTracksNodeRemoval,DestroyProfileOnBrowserClose,DialMediaRouteProvider,GlobalMediaControls,HttpsUpgrades,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartitioning,Transl -main/dist/ripgrep/bin/linux-x64/rg(dns block)If you need me to access, download, or install something from one of these locations, you can either: