Steps to reproduce
- go to https://jsfiddle.net/patrick_h_lauke/w0jaa0vo/1/
- open the file dialog from the first static HTML version of the
<label><input type="file"></label>instance - the dialog opens, you can select a file or cancel it, as expected
- open the second file dialog, this one JS-generated (but the output is exactly the same as the static one). note that whether you select a file or cancel it, the dialog closes and is immediately reopened; this results in an infinite loop of opening file dialogs, whose only escape it to kill the Microsoft Edge process from the Task Manager
this problem does not happen if the
<input> are siblings, rather than being nested.
Comments and activity
related discussion: https://github.com/twbs/bootstrap/issues/20335#issuecomment-235275903
- Microsoft Edge Team
Changed Assigned To to “Bogdan B.”
Changed Status to “Confirmed”
Resolved the other two issues that were duped to the initial creation of this bug since it’s public facing already.
- Microsoft Edge Team
Changed Assigned To from “Bogdan B.” to “Jonathan H.”
Changed Assigned To from “Jonathan H.” to “Bogdan B.”
Changed Status from “Confirmed” to “Fixed”
Thanks for the report, we have fixed the issue in the development version of the browser.
All the best,
The MS Edge Team
Can we know which version of Edge would have the fix?
As of today (Microsoft Edge 38.14393.0.0, Microsoft Edge 38.14393.0.0) fix is still not in Edge.
It’ll be great to know when it’ll be the case
Any update as to when this issue will be solved?
Any updates when this will be released?
When will this fix be made available? Still able to replicate this bug with Microsoft Edge 38.14393.0.0
Do you have any workaround?
Any updates on this? Still seeing the issue and will cause us to discourage our users from using MS Edge.
it’s fixed in insider builds (e.g. Microsoft EdgeHTML 15.15058). assuming this will be available to the general public in the upcoming Win 10 Creators Update in the next few weeks
Hi, i am using windows 10 with all the latest updates but i don’t have the latest version of edge (My version: Microsoft EdgeHTML 14.14393). Is there any workaround to fix this issue ?
Pretty annoying report as fixed over a year ago still an issue.
It’s fixed in Microsoft EdgeHTML 15.15xxx which was released as part of the Windows 10 Creators Update, was rolled out to the public (not just as insider build) end of April / beginning of May.