-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
UI does not work in FF #73
Comments
I just tried opening it in Firefox Quantum 59.0.2 and 60.0.2, and in Safari Version 11.1 (13605.1.33.1.2). I was not able to identify any flaws in the UI on any of the pages. Note that I did not check the functionality. Can we obtain screenshots of what parts of the UI have been reported to not be working in specific versions of Firefox and Safari |
Cool. Have not tested myself, will rope in the person who alerted me to this and see where things actually go wrong. |
@jacogr When using Firefox 60.0.2 on Manjaro/Arch, the UI doesn't display anything when running a node locally. It simply shows a blank page. Works fine via the public UI though, and https://polkadot.js.org/apps/ works fine in Chrome when running my node. |
@phillux Could you go to the "console tab" and screenshot which is no doubt a stream of errors. Ok, so I'll upgrade my FF as well, I'm way behind that. |
Current status - UI does load, however security (as per last screenshot) is still an issue and out of our control. (See the tracking issue #132) Closing since it does render with hosted nodes and the local node issue is tracked in the linked issue. |
@jacogr should we list web browsers in the readme instructions that we recommend to users (that don't generate a security error) |
FF is allowing mix-content on ws://localhost in https://phabricator.services.mozilla.com/D38290 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Safari also not tested - Babel config is set properly, but none of the dev team has actually tried Chrome, alas, reports are there are some issues..
The text was updated successfully, but these errors were encountered: