mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #37] Not Working in IE 11 #15
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @edisonaugusthy on GitHub (Aug 23, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/37
Describe the bug
App Crashes in IE 11
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the view should be the same as in chrome.
Screenshots

Desktop (please complete the following information):
@liyasthomas commented on GitHub (Aug 23, 2019):
I afraid IE 11 lacks ES6 support. And thus broke the app. I regret any inconvince caused. Let me do some more tests and will let you know
@AndrewBastin commented on GitHub (Aug 23, 2019):
Thanks for opening the issue...
I am pretty sure this can be resolved by resolving #31 .
Until then it's impractical to work on IE support while dropping all the niceties of modern JavaScript.
@diego81b commented on GitHub (Aug 23, 2019):
Yeah, vue-cli comes with babel transpiling (more or less @AndrewBastin the same happens in create-react-app).
For working with IE11 we have to pay attention with modern CSS too (for example flex, but there are many others) so question is if we really want the project "IE11 compliant".
Personally i don't find any reason to make it 100% compatible with IE11 also due to the fact that Chrome, Brave and Firefox are free to use browsers for any OS
@AndrewBastin commented on GitHub (Aug 23, 2019):
@diego81b yeah, well the issue opened here is that the app doesn't work on IE11, lending some basic support doesn't hurt.
I don't think we need full IE11 compliance, because that will make it difficult or limit the stuff we can do with this app, but some graceful fallbacks will be nice.
Well, another kinda being a wrench to this is that I am kinda working on making Postwoman kinda run as a lightweight cross-platform native desktop app (still by not using Electron) instead by depending on system webviews, in Windows that will be IE, so well, I kinda would love 100% IE compliance 😅
@liyasthomas commented on GitHub (Aug 25, 2019):
Closing the issue since #51 solved it