Rayan Kanso
Rayan Kanso
For example: '/resources/icons/15.jpg' tries to load the asset at https://peter.sh/tests/random/resources/icons/15.jpg The actual asset is at https://peter.sh/tests/resources/icons/15.jpg on the server.
In the new version of the spec, getting the fetches from the event returns a Promise. `event.fetches.forEach(...)` should become something like `(await event.fetches.values()).forEach(...);`
The spec defines outlines the matching algorithm here: https://w3c.github.io/ServiceWorker/#request-matches-cached-item A Background Fetch should have the same set of restrictions (duplicate URLs allowed only with an appropriate `Vary` header).
Use the ImageResource dictionary defined in the Web App Manifest spec (https://www.w3.org/TR/appmanifest/#imageresource-and-its-members) to pass the icons.
The constructor requires a BackgroundFetchSettledEventInit object, which in turn requires a BackgroundFetchSettledFetches object, which has no constructor.
There's some overlap between the [Media Feeds API](https://github.com/WICG/media-feeds) and Content Indexing. The APIs seem to be solving different problems though. For one thing Content Indexing is more geared towards offline...
Some people have raised concerns that the name of the API is confusing. Is there a better name for this? `Offline Metadata` has been thrown around.
In other words, should an iframe have the ability to register content?
The spec draft implies that a new tab should be opened when the UI is activated. Is that the right thing to do? Should this be more flexible to allow...
It would give users a better idea of how much space they would get back upon deleting an entry, and makes for better UI.