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
When the client is disconnected from the server we need to indicate it in the UI and include a counter to the next try and a button to retry immediately. Currently users lose data because of the absence of this indicator. This is what connected client like Gmail do:
Another possible longer term solution would be to support a full offline mode where unsynced changes are kept on the browser local storage.
The text was updated successfully, but these errors were encountered:
Yes I would also like to support offline mode, in which case it is still relevant to have an indicator in the UI saying “You are in offline mode”.
I played with GroudDB and I’m confident this is a good solution for us. However appcache is deprecated, and the replacing technology is the service worker. I would love to see someone developing an offline package for Meteor using service worker (and I’m not the only one) and if no one is doing it, I may try.
Let’s open a separate thread about offline support and keep this one about the indicator.
When the client is disconnected from the server we need to indicate it in the UI and include a counter to the next try and a button to retry immediately. Currently users lose data because of the absence of this indicator. This is what connected client like Gmail do:
Another possible longer term solution would be to support a full offline mode where unsynced changes are kept on the browser local storage.
The text was updated successfully, but these errors were encountered: