-
Notifications
You must be signed in to change notification settings - Fork 48
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
StyleEditor Errors using Internet Explorer #92
Comments
Currently I use the babel default and everything is transpiled to ES6. |
Got ya, I appreciate it. It would be IE 11 that I'd want to support. |
@kyscott Did this problem resolve? It should work on IE11, as it is only ES5 - but I have no option to test this. |
@fupduck I noticed in the project's package.json that the "main" property points to source code rather than the distribution directory's minified javascript. Could you modify it to point to the minified javascript file? By doing this, I believe @kyscott and everyone else will get access to your transpiled IE 11-compatible code...as the source code itself isn't IE 11-compatible. Many thanks for your help & work! |
@pipedreamer007 Thanks for the hint. |
@fupduck I wanted to know the status of creating a new npmjs package that points to the minified version of leaflet style editor. Is that still an item you are working on since this does resolve the IE 11 compatibility issue for leaflet style editor? |
@EvoDevMan yes - hopefully will have time this weekend |
@fupduck Memo: create option to use travis for publishing |
@fupduck Many thanks for your hard work & excellent plug-in! I actually learned a bit looking at your project. |
@pipedreamer007 thanks this means a lot to me :) |
I noticed an issue with using the StyleEditor in Internet Explorer. When trying to open a page with a Leaflet Map with the StyleEditor integrated, the page doesn't load and the console throws an error. It says that it's looking for a ':' in the Form.js file on the line with the function called "showFormElementForStyleOption". I believe this may be an error with ES6 as everything works fine in Firefox, Chrome and Edge.
Is this is a known issue and is there a possible resolution to make things work in Internet Explorer?
The text was updated successfully, but these errors were encountered: