diff options
| author | Agando <roduccomm@gmail.com> | 2026-11-02 22:02:45 +0100 |
|---|---|---|
| committer | Agando <roduccomm@gmail.com> | 2026-11-02 22:02:45 +0100 |
| commit | ade40a078213c13e093623429bf7c3743c756f3b (patch) | |
| tree | 477ce2f204cd67f3508d7fd64c64385bff3a7023 /modules/core/module-system.js | |
| parent | 46a1b29d1e60fa0ac478fdff45dc6456807d6297 (diff) | |
fix(auth-ui): stop offering a Telegram widget where it cannot work
Two hosts cannot complete the widget flow and both are in use: an Android WebView /
in-app browser (the operator's phone UA ends "; wv)") and a desktop browser that blocks
the popup or hands the link to the Telegram app. The widget needs a popup that can
postMessage back into the opener; in those hosts the link lands in a browser tab or in
Chrome with no opener, onTelegramAuth never fires, and the login card looks dead —
"it opens my default browser" (reported twice: phone, then Max's laptop).
modules/wx11-tg-webview.js (new)
WX11TG.isWebView() -> "; wv)", Telegram in-app, Meta in-app UAs
WX11TG.dropWidgets()-> removes already-rendered oauth.telegram.org iframes/scripts
dashboard.html
code box is open by default and drops the nested <details>
WebView: widget removed + "cannot work inside an app window" hint
desktop: if the widget was clicked and onTelegramAuth has not fired in 12 s, open the
code flow with a hint instead of leaving a dead card
spaces/newos4 (webdav-login panel)
in a WebView the widget is never injected, the mount is hidden and the device-code
flow starts by itself; desktop keeps the widget unchanged
version v4.6.145
Measured with playwright (390x844 WebView UA and 1440x900 Chrome):
WebView -> 0 Telegram iframes, hint shown, code box open, real WX11- code minted
desktop -> widget still rendered, code box open, real WX11- code minted
newOS4 WebView -> no widget injected, code area auto-visible, code WX11-..., no JS errors
newOS4 desktop -> widget still offered
Diffstat (limited to 'modules/core/module-system.js')
0 files changed, 0 insertions, 0 deletions