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
UpUp.isAvailable()
Returns 0 if UpUp requirements aren't supported by current page (e.g. ServiceWorkers, HTTPS, etc.)
Returns 1 if UpUp supported.
Returns 2 if UpUp supported and cache is filled.
The text was updated successfully, but these errors were encountered:
TalAter
changed the title
Allow site to ask UpUpUp if offline mode is available
Allow site to ask UpUp if offline mode is available
Mar 11, 2015
This latter functionality might be more easily addressed once the #42 issue is addressed
Finally, no need for an event emitter for browser support as I think this would always be static (outside of a config change like in Firefox 42 but that's too small a edge case to consider a solution for).
I'm thinking a more generic function than browserSupported()... maybe something like supported() which could also test for other compatibility issues (e.g. HTTPS)
I think those messages serve different audiences ... Meaning the HTTPS issues is more of a developer issue whereas the browser support is more of a dynamic client issue. Still I can see that combining them could make sense from an UpUp perspective. If a developer wants to react to client browser they can pretty easily test for it with window.navigator.serviceWorker.
An idea:
UpUp.isAvailable()
Returns 0 if UpUp requirements aren't supported by current page (e.g. ServiceWorkers, HTTPS, etc.)
Returns 1 if UpUp supported.
Returns 2 if UpUp supported and cache is filled.
The text was updated successfully, but these errors were encountered: