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.

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

Swagger Editor V3 - Safari Support #1244

Closed
ApigeeCorky opened this issue Mar 29, 2017 · 4 comments · Fixed by swagger-api/swagger-ui#2861
Closed

Swagger Editor V3 - Safari Support #1244

ApigeeCorky opened this issue Mar 29, 2017 · 4 comments · Fixed by swagger-api/swagger-ui#2861
Assignees

Comments

@ApigeeCorky
Copy link

ApigeeCorky commented Mar 29, 2017

Rebuilding the latest per issue 1232....Using MacOS Sierra, Safari 10. The editor now displays and works on initial load by typing changes to the spec, but it is very easy for the swagger spec display pane to stop working and stop responding. After loading the editor with the default spec....highlight the entire spec in the editor, delete the contents of the editor, and the console throws an error and the display pane no longer responds to content changes in the editor. (same behavior works fine in chrome and firefox).

Steps to recreate:
Rebuild per issue 1232
Load in safari
Command-A -> Command X to highlight and cut all content out of the editor
Error thrown in javascript console
type anything in the editor, display pane does not respond

speceditor-safari2

@webron
Copy link
Contributor

webron commented Mar 29, 2017

Issue confirmed. Not sure it's related to Safari though, I've seen similar things in other browsers. We'll need to investigate.

@twawszczak
Copy link

Same problems occurs in other browsers. (for example Chrome)

@shockey
Copy link
Contributor

shockey commented Apr 5, 2017

This should be working again when we release new versions of Swagger-UI and Swagger-Editor on Friday. 🍻

@shockey
Copy link
Contributor

shockey commented Apr 8, 2017

Confirmed working for me; releasing version with a fix now.

Please reopen if the problem persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants