You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2018. It is now read-only.
Due to the move to a completely javascript based front end, on slow internet (like conferences), for a second after load all states are visible. This means "sign in", "sign out", the table for the queue, and "Queue is empty" all appear. I think the initial load should do a server side render of the HTML so that your view is correct, and then we can ensure it auto-updates after that. May require moving from Knockout, not sure.
The text was updated successfully, but these errors were encountered:
agreed, and I’d like to move away from knockout if possible. It worked as a proof of concept, but I wasn’t 100% happy with it as an implementation.
In general - happy to drop client side refreshing altogether if you didn’t find it useful.
Due to the move to a completely javascript based front end, on slow internet (like conferences), for a second after load all states are visible. This means "sign in", "sign out", the table for the queue, and "Queue is empty" all appear. I think the initial load should do a server side render of the HTML so that your view is correct, and then we can ensure it auto-updates after that. May require moving from Knockout, not sure.
The text was updated successfully, but these errors were encountered: