-
Notifications
You must be signed in to change notification settings - Fork 1
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
Blocked pop-up #140
Comments
hmm interesting I never get a popup blocking the new tab. I'll look into it ty. either way functionality needs to be improved #134 |
I hadn't noticed the issue before either, so maybe it's because of a recent Chrome update? |
@lucakato No blocked popup but that's because it just opened in the same tab instead of opening a new tab. Was that the intention? |
@kwheelan Not really, because my attempts kept getting the popup blocked. I can't test this on the CLOSUP website (it may fail to load when embedded in another site) but I just talked to Margaret and she said we could just decide not to embed it in website. So we could leave it as is for now? The other option is: |
@lucakato You can definitely try reverting, but I wonder if the issue is a new Chrome version that auto-blocks popups rather than the change to /upload/complete? Anyway maybe it's worth a try to revert and we can test embedded/not embedded and both Safari and Chrome. If that fails, just keeping the site unembedded and never opening a new tab seems like a fine solution to me. |
Related to #134
When the app tries to open a new tab after conversion, both Chrome and Safari block the new tab, sometimes with a warning. This may have been the issue @lucakato you were trying to fix with #118 / #117? That new tab isn't blocked, but it opens too early.
The text was updated successfully, but these errors were encountered: