starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #386] IE Support #141

New issue

Closed

opened 2026-03-16 13:39:04 +03:00 by kerem · 13 comments

kerem commented

2026-03-16 13:39:04 +03:00

Owner

Originally created by @AndrewBastin on GitHub (Dec 1, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/386

Originally assigned to: @AndrewBastin, @liyasthomas on GitHub.

Is your feature request related to a problem? Please describe.
Postwoman is broken in Internet Explorer (tested in IE11)

Describe the solution you'd like
Postwoman should work properly in IE

Describe alternatives you've considered
Not Applicable

Additional context
This feature is crucial for the implementation of the native wrapper ( #267 )

Originally created by @AndrewBastin on GitHub (Dec 1, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/386 Originally assigned to: @AndrewBastin, @liyasthomas on GitHub. **Is your feature request related to a problem? Please describe.** Postwoman is broken in Internet Explorer (tested in IE11) **Describe the solution you'd like** Postwoman should work properly in IE **Describe alternatives you've considered** Not Applicable **Additional context** This feature is crucial for the implementation of the native wrapper ( #267 )

kerem

2026-03-16 13:39:04 +03:00

closed this issue
added the
help wanted

core

critical
labels

kerem commented

2026-03-16 13:39:20 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 1, 2019):

I'll work on it.

@liyasthomas commented on GitHub (Dec 1, 2019): I'll work on it.

kerem commented

2026-03-16 13:39:25 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 1, 2019):

Babel transpiled build throws syntax error.
But at least I was able to get Nuxt error page! I've hope.

@liyasthomas commented on GitHub (Dec 1, 2019): Babel transpiled build throws `syntax error`. But at least I was able to get Nuxt error page! I've hope.

kerem commented

2026-03-16 13:39:30 +03:00

Author

Owner

@NBTX commented on GitHub (Dec 1, 2019):

@liyasthomas have you tried transpiling to an older destination in babel?

@NBTX commented on GitHub (Dec 1, 2019): @liyasthomas have you tried transpiling to an older destination in babel?

kerem commented

2026-03-16 13:39:35 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 1, 2019):

Nope. I went with the latest version. But i dont think babel is the reason, I think it's an issue with template literals etc.

@liyasthomas commented on GitHub (Dec 1, 2019): Nope. I went with the latest version. But i dont think babel is the reason, I think it's an issue with template literals etc.

kerem commented

2026-03-16 13:39:40 +03:00

Author

Owner

@NBTX commented on GitHub (Dec 1, 2019):

@liyasthomas yeah You actually want to select an older destination version - if you make it target internet explorer and other older browsers, Babel will polyfill missing features such as template literals (which IE doesn't support)

Edit: see https://babeljs.io/docs/en/usage#configuration

@NBTX commented on GitHub (Dec 1, 2019): @liyasthomas yeah You actually want to select an older destination version - if you make it target internet explorer and other older browsers, Babel will polyfill missing features such as template literals (which IE doesn't support) Edit: see https://babeljs.io/docs/en/usage#configuration

kerem commented

2026-03-16 13:39:45 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 1, 2019):

Okay, will try with a lower version and let you know.

@liyasthomas commented on GitHub (Dec 1, 2019): Okay, will try with a lower version and let you know.

kerem commented

2026-03-16 13:39:51 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Dec 3, 2019):

Sooo, any updates ?

@AndrewBastin commented on GitHub (Dec 3, 2019): Sooo, any updates ?

kerem commented

2026-03-16 13:39:56 +03:00

Author

Owner

@mabushey commented on GitHub (Dec 19, 2019):

Who runs IE? What a joke. I hope the Postwoman codebase is not cluttered with hacks to "fix" this.

@mabushey commented on GitHub (Dec 19, 2019): Who runs IE? What a joke. I hope the Postwoman codebase is not cluttered with hacks to "fix" this.

kerem commented

2026-03-16 13:40:01 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 19, 2019):

IE support is mainly required for offline build which is a WIP.

@liyasthomas commented on GitHub (Dec 19, 2019): IE support is mainly required for offline build which is a WIP.

kerem commented

2026-03-16 13:40:06 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Dec 19, 2019):

@mabushey Thank you for voicing your concerns, and yes no one practically uses IE, especially in our target audience. But we do need IE support to implement a lightweight native client solution for Postwoman.

I am trying my best to not pollute the codebase for IE support, most of the work needed for IE support is just optionally loading separate scripts for implementing the missing behaviors in IE and to ensure the generated Postwoman code is suitable for IE. None of the changes introduced/proposed so far has brought changes to the main Postwoman code.

I usually also discuss the changes I bring before I work on them on Telegram/Discord.

@AndrewBastin commented on GitHub (Dec 19, 2019): @mabushey Thank you for voicing your concerns, and yes no one practically uses IE, especially in our target audience. But we do need IE support to implement a lightweight native client solution for Postwoman. I am trying my best to not pollute the codebase for IE support, most of the work needed for IE support is just optionally loading separate scripts for implementing the missing behaviors in IE and to ensure the generated Postwoman code is suitable for IE. None of the changes introduced/proposed so far has brought changes to the main Postwoman code. I usually also discuss the changes I bring before I work on them on Telegram/Discord.

kerem commented

2026-03-16 13:40:11 +03:00

Author

Owner

@NBTX commented on GitHub (Dec 20, 2019):

@mabushey I can confirm - on account of IE support not even being present - that nobody who uses postwoman does so with IE.

The reason we're even considering IE support is that we need some way to get around CORS restrictions. Postman got around this with electron, but we've avoided doing the same as we've found it to be bulky and slow - plus it's got all of Chromium's notorious memory issues.

Thus, in order to avoid using electron, @AndrewBastin was trying to build a native version that simply used whatever browser rendering engine came on the OS by default. Sadly, on Windows, that's still Internet Explorer - even in the latest versions of Windows 10. Hence, we have been investigating and trying to implement IE support.

I do feel that as our biggest user audience is most likely on Windows, we should avoid IE at all costs given it would be, frankly, a second-rate experience - not to mention that the browser is essentially put on the back-burner by Microsoft. Hence, my preferred solution is to use a locally installed proxy server which would avoid this problem, though it remains to be seen how usable the proxy is.

(You can see some details of how the proxy would be implemented here) https://github.com/liyasthomas/postwoman/issues/267#issuecomment-567904336

@NBTX commented on GitHub (Dec 20, 2019): @mabushey I can confirm - on account of IE support not even being present - that nobody who uses postwoman does so with IE. The reason we're even considering IE support is that we need some way to get around CORS restrictions. Postman got around this with electron, but we've avoided doing the same as we've found it to be bulky and slow - plus it's got all of Chromium's notorious memory issues. Thus, in order to avoid using electron, @AndrewBastin was trying to build a native version that simply used whatever browser rendering engine came on the OS by default. Sadly, on Windows, that's still Internet Explorer - even in the latest versions of Windows 10. Hence, we have been investigating and trying to implement IE support. I do feel that as our biggest user audience is most likely on Windows, we should avoid IE at all costs given it would be, frankly, a second-rate experience - not to mention that the browser is essentially put on the back-burner by Microsoft. Hence, my preferred solution is to use a locally installed proxy server which would avoid this problem, though it remains to be seen how usable the proxy is. (You can see some details of how the proxy would be implemented here) https://github.com/liyasthomas/postwoman/issues/267#issuecomment-567904336

kerem commented

2026-03-16 13:40:16 +03:00

Author

Owner

@liyasthomas commented on GitHub (Feb 9, 2020):

I think this issue is stale now and should be closed. @AndrewBastin what do you say?

@liyasthomas commented on GitHub (Feb 9, 2020): I think this issue is stale now and should be closed. @AndrewBastin what do you say?

kerem commented

2026-03-16 13:40:21 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Feb 9, 2020):

Yeah sure, I don't think IE support is something that is in immediate need. Or actually in a need ever at all 😅 (thank god)

@AndrewBastin commented on GitHub (Feb 9, 2020): Yeah sure, I don't think IE support is something that is in immediate need. Or actually in a need ever at all :sweat_smile: (thank god)