Skip to content
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.

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

Account verification not reactive across windows #297

Open
th0rgall opened this issue Jan 25, 2023 · 0 comments
Open

Account verification not reactive across windows #297

th0rgall opened this issue Jan 25, 2023 · 0 comments

Comments

@th0rgall
Copy link
Contributor

th0rgall commented Jan 25, 2023

Since the fixes mentioned here #98 (comment), the following scenario works:

  1. Create an account in tab A in window W
  2. Open a verification link via email in tab B in window W
  3. Both tab A & B will have been notified of a fully verified account.

However, these updates don't seem to propagate across windows:

  1. Create an account in tab A in window W (e.g. on your mobile phone)
  2. Open a verification link via email in tab B in window D (e.g. on your desktop)
  3. The account Tab A will be unverified until you reload the page.

There are also different scenarios possible for how Tab B looks when opened in a different context from tab A. See #298.

th0rgall added a commit that referenced this issue Jan 26, 2023
Should fix #298.
Mitigates #297 somewhat, in the sense that this adds proactive one-time checks/state reloads when the user tries to access a resource that is verification-depedent client-side. No verification state streaming yet (only possible via Firestore), but this should already reduce the UX friction that exists today when verifying on a different device/window, especially in combination with the ReloadSuggestion component.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant