Skip to content

fix: Chrome 78 compat and AudioWorklet multi-run display#22

Merged
fan-droide merged 2 commits into
mainfrom
webcomponent
Jun 10, 2026
Merged

fix: Chrome 78 compat and AudioWorklet multi-run display#22
fan-droide merged 2 commits into
mainfrom
webcomponent

Conversation

@fan-droide

Copy link
Copy Markdown
Collaborator

Summary

  • Replace ?? nullish coalescing in demo/js/common.js with an explicit ternary — ?? is a parse error in Chrome 78 (landed in Chrome 80), which prevented common.js from loading entirely
  • Replace ac?.close() with if (ac) ac.close() in src/dev-test/index.js and src/dev-test/gain.js — same Chrome 78 parse-error issue on the dev-test connect button
  • Remove currentLatency.textContent = '' from the latency-recording handler in demo/js/audioworklet.js — the AudioWorklet multi-run panel was clearing the previous result on each new recording, unlike the multi-run panel which preserves it

Test plan

  • Chrome 78: connect button in demo and dev-test pages responds (mic permission prompt appears)
  • Modern browser: connect button still works; AudioContext is closed on getUserMedia failure
  • AudioWorklet panel, multi-run: previous latency value stays visible while next run is recording

🤖 Generated with Claude Code

gilpanal and others added 2 commits June 10, 2026 15:15
… panel

latency-recording handler was clearing currentLatency, hiding intermediate
results between runs. Matches the existing multi-run panel behaviour.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@fan-droide
fan-droide merged commit 337cdf9 into main Jun 10, 2026
2 checks passed
@fan-droide
fan-droide requested a review from gilpanal June 10, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants