-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
waymarkedtrails no longer works with older browsers #405
Comments
The new version of the site needs a browser with ES2020 compatibility. According to MDN that means Firefox 67. Seamonkey looks to be stuck with Firefox 60. There is probably a lot that can be done with the help of Babel in terms of compatibility for older browsers. But it's the kind of rabbit hole that is hard to get out of once you are inside. So I'm sorry to say that I probably won't spend time on it. I will happily take Pull Requests, though. The repo in question is https://github.com/waymarkedtrails/waymarkedtrails-website. This is a simple Svelte/Javascript application. You don't need to set up a full database to contribute. It happily runs against the API on waymarkedtrails.org. |
Thanks for the info. I posted on a Seamonkey list/group and got a reply from (I think) one of the developers, who said your site is using a dynamic module import from the ES2020 spec which is not supported by Seamonkey yet; eventually will be but not for at least a few months. (Not clear why you said ES6 and they said ES2020 but same result.) I absolutely agree this is not worth changing on waymarkedtrails.org. As another example, I am using Firefox to add this comment because github is really flakey with Seamonkey. |
I've edited my comment regarding ES2020. For others with a similar issue, here is the compatibility list from caniuse: https://caniuse.com/es6-module-dynamic-import |
I have used Waymarkedtrails with the Seamonkey browser (https://www.seamonkey-project.org/) but recently the site no longer works. Only a blank page is displayed.
My browser error log has this:
Sorry, I can't pin down exactly when this started.
Is this a browser problem, or a site problem?
The text was updated successfully, but these errors were encountered: