L'esperienza di Tecnoblog con i commenti di Discourse

Falco · 15 Maggio 2026, 5:09pm

Thiago_Mobilon:

5. Attrito durante l’accesso

Il flusso attuale è un po’ un killer di conversioni: l’utente clicca su accesso → si apre una nuova scheda → avviene l’accesso → l’utente si ritrova sulla homepage della community. Tornando sul post del blog, l’iframe appare ancora come non autenticato finché l’utente non aggiorna manualmente l’intera pagina. È un ciclo confuso che fa desistere le persone e le porta ad abbandonare il post prima di poter commentare.

Dall’attivazione del nuovo embed, i nostri registri giornalieri sono più che raddoppiati, il che è fantastico. Tuttavia, le nostre metriche di engagement non sono cambiate affatto. In realtà, il nostro DAU/MAU è diminuito – abbiamo più utenti autenticati, ma non interagiscono. Metriche come “Utenti attivi giornalieri”, “Nuovi contributori” e “Pubblicazioni” non hanno visto alcun aumento.

Questo dimostra che le persone vogliono partecipare alla conversazione, ma si perdono nel ciclo di accesso e abbandonano il post prima di poter effettivamente commentare.

Questo è ora risolto, si prega di aggiornare per ottenere il nuovo flusso di accesso.

github.com/discourse/discourse

FEATURE: Add in-iframe sign-in flow for full app embed mode (#39756)

main ← embed-full-app-signin-flow

merged 04:07PM - 15 May 26 UTC

xfalcox

+644 -4

Previously, full app embeds loaded on a third-party domain could not see the for…um's session cookie, leaving users effectively logged out, and `showLogin` only opened a dead-end `/login` tab the iframe never reacted to. This adds an `embed_full_app_signin_flow` site setting (on by default, gated to full app embed mode) that intercepts logged-out actions inside the iframe with a guided flow: bridge storage access if the iframe's cookie jar is partitioned, then either reload (if the user is already signed in elsewhere) or open a top-level sign-in tab and watch the session via polling. ## Flow 1. User clicks an auth-gated action (Reply CTA, Like, etc.). `showLogin` / `showCreateAccount` and the embed-topic-footer reply CTA route into the new `embed-auth-flow` service. 2. **If `document.hasStorageAccess()` is `false`** — Safari ITP, Firefox Total Cookie Protection, Chrome's 3p cookie phaseout — an in-iframe modal asks the user to share their session. Confirming calls `requestStorageAccess()` (synchronously inside the click handler so user activation is preserved). 3. Once we have access, the service probes `/session/current.json`. If the user is already signed in elsewhere (common Firefox ETP scenario), the iframe reloads to pick up the session — no popup. 4. Otherwise, a sign-in modal opens a top-level `/login?embed_signin_callback=1` (or `/signup`) tab and shows a waiting state with a spinner. The iframe polls `/session/current.json` every 3s for up to 5 min. 5. When polling sees a logged-in response, the iframe reloads. The popup self-closes once it has a session, driven by the `embed_signin_callback` query param + sessionStorage flag. ## Why polling instead of `postMessage` The popup-side callback originally posted a success message back to the opener. Discourse's default `Cross-Origin-Opener-Policy` (`same-origin-allow-popups`) typically mismatches an embedding host's (`unsafe-none`), which severs `window.opener` on the popup's very first load — and any OAuth provider redirect amplifies this. Polling sidesteps the whole opener relationship and works regardless of COOP, OAuth, or the user opening the link in a new tab. ## Setting - `embed_full_app_signin_flow` (boolean, default `true`, in the `embedding` area). - The flow assumes the iframe can receive its cookies after popup sign-in — true when the embed is **same-site to the host page** (any SameSite setting) or when `same_site_cookies = "None"` is configured for cross-site embeds. We trust the admin to enable this only on a compatible deployment. ## Implementation notes - **Browser-agnostic storage access.** `hasStorageAccess()` is the single signal — `true` on same-site/same-origin embeds (no prompt needed), `false` whenever the iframe's cookie jar is partitioned. No browser sniffing. - **User activation preserved.** The modal uses native `<button {{on "click" handler}}>` rather than `service:dialog`, so `requestStorageAccess()` and `window.open()` see a live activation token in the click handler. - **No reload after storage access.** `requestStorageAccess()` grants access for the current document; we chain directly into the next step in the same execution. Reloading would put the iframe back in partitioned mode in most browsers. - **Popup self-close is param-driven, not opener-driven.** The callback initializer keys off `?embed_signin_callback=1` alone — `window.opener` is unreliable thanks to COOP. - **API-unsupported fallback.** Without `document.requestStorageAccess`, the service opens a plain top-level login tab (no callback param) instead of trapping the user in a popup that cannot bridge cookies. - **Storage access denial is a dead-end on purpose.** The catch handler does not chain to a sign-in popup, since a sign-in tab cannot help an iframe that lacks storage access. The user retries the action to be re-prompted. - **Waiting modal.** While polling, the iframe shows a spinner and "Waiting for sign-in" message. Cancel stops the poll and closes the popup; the modal auto-dismisses on timeout. ## Tests `tests/unit/services/embed-auth-flow-test.js` covers gating, the partitioned vs. non-partitioned split, the storage-access → sign-in chain, the already-signed-in → reload path, denial behaviour, popup URL routing, and the API-unsupported fallback.

Argomento		Risposte	Visualizzazioni
Embed Discourse comments on another website via Javascript Integrations embedding , how-to	127	306272	Giugno 2, 2026
Embed Discourse comments with on-page commenting? Feature	32	8463	Gennaio 19, 2019
Embed Discourse as a full comment system on your site Announcements embedding	27	3118	Ottobre 10, 2026
Discourse Comments stuck on "Loading..." Support	22	2381	Settembre 18, 2024
Should Discourse make an effort to become a viable comment platform? Community Building	62	6008	Marzo 25, 2026

L'esperienza di Tecnoblog con i commenti di Discourse

Argomenti correlati