Originally created by: kristofferR
fMess reports that Facebook keeps its WebKit frame-encryption path (RTCRtpScriptTransform) for calls in end-to-end encrypted chats behind gatekeeper 16078. Without it, Messenger may refuse calls in encrypted chats on WebKit even when the engine supports script transforms. Chatpane fixed the user agent (#343), but has no gatekeeper override, and lib/calls.ts:14-22 assumes script-transform support is enough.
On the Mac, place a voice and a video call in an encrypted chat (and one in a non-encrypted chat for comparison). If it works, close this issue with the result.
gkx("16078") = true (fMess: 03-facebook-modules.js:25-37), on macOS only, through Chatpane's existing module-hook mechanism.popup-* call windows, which Chatpane's injection currently skips (window.rs:140). Inject only this narrow call-compat patch there, not the full feature bundle.Encrypted-chat calls on macOS: outgoing and incoming, voice and video, audio both ways, camera on/off, ending the call closes the popup.
Part of [#349].