Skip to content
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.

Sign up for GitHub

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

Jump to bottom

See about making the JS partially work on older browsers #55

Open
fluffy-critter opened this issue Dec 4, 2019 · 0 comments
Open

See about making the JS partially work on older browsers #55

fluffy-critter opened this issue Dec 4, 2019 · 0 comments
Labels
flask Functionality relating to the built-in Flask wrapper low priority Things that are nice to have but not a big deal UX Relating to the end-user experience

Comments

@fluffy-critter
Copy link
Contributor

If the JS code can be structured such that there's no top-level async functions, and old browsers (e.g. IE11) simply elide the attempt to check the remote URL, older browsers could at least have the enable/disable flag working on the button. Which is a slight, if trivial, improvement.
@fluffy-critter fluffy-critter added flask Functionality relating to the built-in Flask wrapper UX Relating to the end-user experience low priority Things that are nice to have but not a big deal labels Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flask Functionality relating to the built-in Flask wrapper low priority Things that are nice to have but not a big deal UX Relating to the end-user experience
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fluffy-critter