Notifying users of changes to your #PWA is hard. We’re thinking about ways to make it easier by enabling you to include a version number and point to an HTML change log, RSS/Atom feed, or similar from within your web app manifest. Feedback appreciated!https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/VersionHistory/explainer.md …
Servers deploying mutiple files instead of one in the correct order across global frontends is tricky. Is there evidence of pain that should cause us to prefer multiple files, e.g. download time? If it's just editor preference, that seems like something we could off on.
-
-
Other issues: how will we surface a missing metadata file on devtools? If I delete a manifest for an app but not the metadata file, what happens? Is this metadata file scoped exactly the same way? How does it interact with origin-wide configs like Origin Policy? Versioning?
-
With enough elbowgrease from everyone, I presume all of this can be worked out. Just wondering why we need to work it out *now*; that's all.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.