mirror of
https://github.com/discourse/discourse.git
synced 2026-08-08 20:18:23 -05:00
Régis Hanol
61b0a3730b
On "slow" computers and/or in production builds of the client-side application, the redirection to discourse connect (via window.location) might happen _after_ the login/signup route is done loading and the login/signup template is being shown. Since when discourse connect is enabled, no other auth "provider" is allowed, we "flashed" a screen that indicated there was no "login method" configured. In order to fix this, we rely on the "isRedirectingToExternalAuth" boolean and ensure it's set to "true" when discourse connect is enabled. This is unfortunately ~~impossible~~ very hard to test as it depends on how fast the browser running the test is... The only way I was able to reproduce this issue locally was to throttle both the CPU and network in Chrome's performance tab. <img width="861" height="156" alt="Screenshot 2025-08-07 at 13 43 09" src="https://github.com/user-attachments/assets/de02be42-9ce8-4253-8c9c-fd9784a9bb65" /> --- I also renamed `isRedirecting` to `#isRedirecting` to better indicate this is a private variable. --- **BEFORE** https://github.com/user-attachments/assets/568052d9-70eb-4d27-8d59-a4b67ae6d8ac **AFTER** https://github.com/user-attachments/assets/f51ee3f4-3322-4fc8-8e9b-6195413bba12