-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Dialog does not open in Edge #2146
Comments
Hey guys.....Actually, John this is the exact same bug I've been talking to you about with iOS. Might be actually easier to trace what is going on with edge browser. Here is my video about it. https://youtu.be/I_Ghdsu6aLk (dialogs work in 0.16.1 and fail in 0.16.5 |
The new z-index functionality utilizes for..of quite extensively. When a HTMLElementList is iterated on using for..of and the list is empty, causes Edge to throw a Symbol.iterator fatal fixes #2146
Looks like edge doesn't support iterating over #2150 Will fix this without a polyfill by converting the |
* fix($browser): iPhone iOS click-outside bug iOS does not allow click events to be bound to the body, this is the entire purpose of v-app. Was mistakenly allowed to be removed with PR #1932 * fix($browser): Edge bug with for..of The new z-index functionality utilizes for..of quite extensively. When a HTMLElementList is iterated on using for..of and the list is empty, causes Edge to throw a Symbol.iterator fatal fixes #2146 * refactor: Change forEach to an iterator & update comments to be clearer Converting the NodeList to an array is enough to fix the issue, but this wasn't reflected in the comments * Update click-outside.js
Steps to reproduce
Versions
Vuetify 0.16, Windows 10, build 1703, Edge 40.15063.674.0
What is expected ?
dialog should render
(in my memory this feature worked on edge in the previous release)
What is actually happening ?
nothing visible changes.
If console is open the message is "Object doesn't support property or method 'Symbol(Symbol.iterator)'"
Reproduction Link
https://vuetifyjs.com/components/dialogs
The text was updated successfully, but these errors were encountered: