-
Notifications
You must be signed in to change notification settings - Fork 62
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
Popup should not close on file navigation initiated by the popup #325
Comments
On further testing, Chrome actually does behave this way, but Firefox does not. |
Hi @AidanWelch It looks like a Chrome bug. There was a discussion and a bug for it. But it seems to have been fixed. I can't reproduce this problem in a simple example. If you can, please file a bug and close this issue (because browser-specific bugs are not discussed here). |
The issue doesn't occur on Chrome, and as far as I know it isn't an intended feature of Firefox as it doesn't happen in Firefox. I think it is instead an asynchrony in the standard. (Chrome behaves how I described, Firefox doesn't) |
Do you means it works on Chrome but doesn't work on Firefox? Then it is a Firefox bug. Normally, using |
Yeah
Oh okay, I understand. I thought it was intended in Firefox. |
There are some existing, old, bugs for Firefox. |
Presently, if trying to either saveAs or input a file to a browser extension you have to create a separate tab, and it cannot be done in popup. Clicking within the file navigation initiated by the popup should not close the popup, allowing the popup script to actually be used for file inputting and outputting.
This does slightly expose a risk of a malicious popup spamming file navigation popups, but that doesn't justify removing the functionality entirely. This change would improve both user and developer experience.
The text was updated successfully, but these errors were encountered: