Skip to content

[loop cycle 3] feat(calls): expose minimal window.chrome so WhatsApp enables call buttons #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
karem505 merged 1 commit into from
Jun 28, 2026
Merged

[loop cycle 3] feat(calls): expose minimal window.chrome so WhatsApp enables call buttons #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions src-tauri/resources/bridge.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,23 @@
}
} catch (e) {}

// 1b) Chrome environment marker — enables voice/video CALLING. WhatsApp Web gates
// calling behind a Chrome/Edge eligibility check that, beyond the UA and
// userAgentData (both already spoofed above), probes for `window.chrome`. WebKitGTK
// ships WebRTC (so calls CAN work once eligible) but exposes no `window.chrome`, so
// the call buttons stay disabled. Add a minimal, idempotent stand-in matching what a
// real Chrome minimally exposes; never clobber a genuine `window.chrome`.
try {
if (!window.chrome) {
Object.defineProperty(window, "chrome", {
configurable: true,
enumerable: true,
writable: true,
value: { app: { isInstalled: false }, runtime: {} },
});
}
} catch (e) {}

// 2) Notification override — forward to a native OS notification via Rust.
try {
function ShimNotification(title, options) {
Expand Down
Loading