-
Notifications
You must be signed in to change notification settings - Fork 111
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
bootstrap3-wysihtml5.all.min.js, line 3 character 22397 #30
Comments
Is this an error in Windows 7 or Windows 8? |
Hello, that error is in both 7 and 8. 發自我的小米手機 Christian Sterzl notifications@github.com提到: Is this an error in Windows 7 or Windows 8? Reply to this email directly or view it on GitHub: |
Ok, I found the error. When adding additional shortcuts, I use a reference to body in the iframe. But in IE10 the body is not created when an iframe is created. The reference will if no body is available listen on the iframe itself. I will push it as 0.2.8.alpha soon. |
Can you try it? |
Dear Waxolunist, Thanks for your quick help, but it's still no good. I used your newly built alpha and with full include, the error seems not on yours, but wysihtml5-0.0.3.js. I used your new index-multi-dev.html, only the first textarea display correctly. SCRIPT5007: Unable to get property 'addEventListener' of undefined or null reference wysihtml5-0.3.0.js, line 4658 character 5 Is it working your IE10? Do I miss anything? Regards, |
Ok, seems I forgot to build it actually. I made the change in the source files and forgot to push the dist folder acutally. Can you try it again? It works for me in a virtualbox machine with IE10 and Windows 8. |
I pushed v0.2.8-alpha.2 |
Yes, it works perfectly now! Thanks a lot!!! |
When using IE10 with multiple textareas, only the first one is appearing correctly. The rest are in HTML code. IE10 has this error message "SCRIPT5007: Unable to get property 'addEventListener' of undefined or null reference
bootstrap3-wysihtml5.all.min.js, line 3 character 22397"
All other browsers (IE11, Chrome 32 and Firefox 26) are working fine.
Any idea? Cus' my clients are still using IE10 as their major browser! Please help.
The text was updated successfully, but these errors were encountered: