When it comes to features, Edge has the one critical item that always kept me crawling back to Chrome. If you are on a webpage, you can easily turn it into an app, by clicking the three dots in the top right and clicking install app. This is huge, as it allows me to turn Google Calendar, Tweetdeck, and a few other pages into applications on my desktop that makes my workflow, a lot easier.
we should definitely whitelist all Chrome based browsers @falco
We want to get this working, but the last time we tried with the “You are offline” page wasn’t a great experience. Also we had a lot of suggestions about making reading Discourse possible when you are offline.
The current changes only affect GET requests, so it will make you able to use the composer, if you ever did it while online.
Discourse already keeps submitting a topic in a persistent “Saving” blue bar, and this doesn’t touch that request, so it should keep the current behavior.
However, getting Discourse to work totally in write mode while offline would require a lot more work and be a long term project involving multiple people. That is not the scope here, which is just enabling installs in Desktop.
It’s in the same branch as always here. You could deploy from that branch but it is a lot behind master currently. I can rebase it to master, but I don’t recommend messing with this until it’s proven stable here.
Another cool thing, if you try to use the pwa with a cold cache:
I’ve been googling around on the Chrome side, but couldn’t find anything. So I guess I’ll ask them.
Is this something that could theoretically be dismissable (e.g. with localstorage) or hidden permanently based on a Discourse setting? I’m asking because I don’t know if Chrome automatically detects if the website is compatible as a PWA or if there’s some flexibility on your end to only offer the option conditionally.