-
Notifications
You must be signed in to change notification settings - Fork 251
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
Uncaught TypeError: styleSheet.cssRules[Symbol.iterator] is not a function #618
Comments
What version of Atom are you running, and what operating system are you using? |
Also, are you SURE you're using the latest version of |
Do you mean You also haven't told us your operating system... |
the atom version I have seen wrong, is the version 1.11.2, I will update right now |
And my operating system is Fedora 22 |
Do you have automatic updates turned off? You should really be keeping them enabled, because your Atom version hasn't been updated in 8 months... Another user reported the same issue in March, and they were running an even older version of Atom. I'm wondering if I shouldn't just crank the minimum required Atom version to something more recent... |
This atom is from pc from my office, I don't know if the updates are turn on or off, but I don't find nothing like that on atom. do you know where is that option? |
Are you still seeing this error after installing Atom v1.18? |
I can't update the atom, I don't know why |
Try doing a fresh install using the latest version from |
Finally got to the bottom of this. Gonna post my research here for posterity's sake... After installing Atom v1.11.2 on a virtual machine, I inspected Now, that particular version of Atom ran Chrome 49, and iterator support in DOM interfaces didn't land until Chrome 51. Meaning that array-like DOM objects (e.g., for(let i of document.styleSheets[0].cssRules); // <= Chrome 50: Breaks
for(let i of document.styleSheets[0].cssRules); // >= Chrome 51: Works |
I have update the package yesterday, and always I open the atom this error apears:
what can I do?
The text was updated successfully, but these errors were encountered: