Swagger-ui: 'Try it out' misbehaving in edge

Created on 8 Aug 2017 · 8Comments · Source: swagger-api/swagger-ui

Issue is occurring in V3, and seems to be independent of the document used. It is reproducible with http://petstore.swagger.io/v2/swagger.json

No failures indicated in the developer tools.

It is unclear at this time whether this is an issue with edge or with the swagger-ui. I am hoping someone might be able to provide some insight into what might be happening here. Otherwise, I am reaching out to the edge folks to see if the issue is on their end.

Edge Version: 40.15063.0.0

lock-bot

Source

JoshuaWhatley

Most helpful comment

I think this is related to https://github.com/swagger-api/swagger-editor/issues/1371 - the OP in that ticket was using the same Edge version as you.

An inability for Swagger-UI to read the Content-Type header would cause the Unknown response type message, and the underlying Edge bug in the ticket linked has to do with Edge implementing a nonstandard interface for fetch headers.

Try using the workaround I mentioned there - if you remove window.fetch before instantiating Swagger-UI, the polyfill we being with us _should_ take over and not give you any issue.

shockey on 8 Aug 2017

👍2 🎉1

All 8 comments

@JoshuaWhatley which version of swagger-ui exactly have you tested this with?

webron on 8 Aug 2017

I am using 3.0.17. But I was able to reproduce this on petstore.swagger.io I am assuming the most recent version is hosted there?

This doesn't seem to occur with every version of Edge, so I imagine this issue is likely on their end.

JoshuaWhatley on 8 Aug 2017

I think this is related to https://github.com/swagger-api/swagger-editor/issues/1371 - the OP in that ticket was using the same Edge version as you.

Try using the workaround I mentioned there - if you remove window.fetch before instantiating Swagger-UI, the polyfill we being with us _should_ take over and not give you any issue.

shockey on 8 Aug 2017

👍2 🎉1

Thanks @shockey, I'll add that polyfill and wait on their fix.

JoshuaWhatley on 9 Aug 2017

Looks like this is a problem still in 3.12?

vaustral on 13 Mar 2018

@vaustral yep, nothing was fixed on our end since it’s a browser bug. see the comments and links above for ways to mitigate the problem 😀

shockey on 13 Mar 2018

Ah thanks, i didn't even see it.

vaustral on 13 Mar 2018

Locking due to inactivity.

This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.

If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.

Thanks!