-
Notifications
You must be signed in to change notification settings - Fork 29
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
Project: Classify page allows the classifier tutorial to appear when other modals are already open. #2909
Comments
The |
The classifier is detecting that I'm not logged in, and correctly opening a tutorial in that case. It doesn't know that there's also a login form open, since the login form is controlled by the containing page, so the tutorial opens on top of the existing form. |
You can also reproduce this on In The Spotlight. Choose a workflow and the tutorial will appear before you can choose a subject set, because tutorials listen to changes in |
I think this bug also affects workflow selection: |
See also the comments here. The active tutorial appears when |
This is a bit of a hack, but the Classify page could pass a |
We could also extract There's a related bug when both the popup workflow menu and the login form are open at the same time. Try it here: https://www.zooniverse.org/projects/humphrydavy/davy-notebooks-project/classify?login=true |
Based on @goplayoutside3's comments on #2904, the Transformers project on staging might be a good place to test these bugs eg. |
Package
app-project
lib-classifier
Describe the bug
After signing out then signing back in again, the workflow tutorial appears on top of the sign-in popup.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The tutorial shouldn't be shown until after login is resolved.
Additional context
The browser console showsThe missing task annotation in the screenshot is a red herring. It's bug #2891, which is fixed on staging but still open in production.annotation missing for T1
and the classifier is empty (no subject or task) so it seems like the store is getting itself into an unexpected state.The text was updated successfully, but these errors were encountered: