-
Notifications
You must be signed in to change notification settings - Fork 11
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
WebSockets not degrading gracefully? #35
Comments
The rendering of pagelets should not be affected by the real-time connection that BigPipe creates. The only thing a pagelet needs to renders is:
The real-time connection does not affect anything here. For the search pagelet it would only be used when you actually search and I don't think that the status pagelet requires any real-time connection either. By checkout of the screenshots we can see that the HTML and CSS is already shown on the page which means that all assets have been loaded correctly (as it's styled). Because it only shows a dropdown element in the search pagelet we can safely assume that there's an issue with the execution of the javascript. It probably missed a |
Anyways, master is now using SockJS instead of WebSockets. After we've updated our servers it will also run the latest big pipe so I hope this solves a large portion of the issues that you were seeing. |
So I happen to be trying to visit this on shitty airplane WiFi which I don't think supports WebSockets which is causing this behavior.
Tried to compile as much Network information from Chrome and Firefox as I could
The text was updated successfully, but these errors were encountered: