Super detailed post by @simonhearne on racing the browser cache against the network: https://t.co/sig6WzVPON. https://t.co/gK9WcIDsvC
RT @ChromiumDev: Flexbox gap!
Need some background, want to know timing of when it hits Chrome stable, or to just ramp up in general!? CS…
@SimmerVigor Some well deserved REST…
@Anoesj Yes, this should be it for now. There’re probably going to be more changes in the future: https://t.co/QOeKqKsgKX.
@Anoesj You can transparently switch from v1 to v2 simply by removing the v1 token, but again be aware of the code changes (hence the pointer to browser-nativefs).
Your app sounds really interesting, hope to learn more :-)
@Anoesj There’s a new origin trial going on for v2 of the API with some minor changes: https://t.co/xTo8zYJdqL. If you use the browser-nativefs library (https://t.co/8GMIc3utO1), these changes are taken care of. Good luck with your project. Is it public
RT @ChromiumDev: A couple of the Project Fugu 🡠folk (virtually) presented a demo paper at The Web Conference (@TheWebConf) in April:
🔄 Pa…
@AutomatedTester @cwiiis In the case of the Play Store, it’s in my opinion not about _prioritizing_ PWAs over native apps, but about positioning them _equally_. It’s a journey with the occasional bump, but it has started: https://t.co/xZsWlEJ9xT.