Rayan Kanso

Thanks for the feedback @comp615. You make some good points, but I really don't think enforcing something like that belongs in the spec. As I said in a comment above,...

Currently, the `contentdelete` event only fires if the deletion was originated by the user. But like the idea of have generic `contentadd` and `contentdelete` events. Even though there are workarounds...

Thanks for bringing this up @rektide. The scenario you described is what I've been looking into for the next version of the API, to enable users sharing content index entries....

> Wouldn't any entry-deletion UI be provided by the registering website, rather than the browser Ideally the website should have an entry-deletion option, but it **must** be provided by the...

It might be better to have the promise resolve to true/false depending on whether something was deleted, to match the CacheStorage API.

I agree with all the points you made. The categories in the explainer are currently undescribed and a bit hand-wavy. The point of that field is to give a hint...

I'm not sure what advantage providing the display language would provide. Unicode allows for encoding the text direction. Notifications properly display CJK and RTL languages, and only the string is...

I'm wary of adding any more fields to the already pretty large `ContentDescription` dict. It only contains the information the browser needs to know at registration time at the moment....

> `registration.index.add()` currently rejects if you pass in an `icons[].src` value that isn't a valid URL What's an invalid URL in this case? I can't see the sample code, and...

The URL spec defines comparing two URLs [here](https://url.spec.whatwg.org/#url-equivalence), which would apply to point 4.6. Step 4.1 uses string comparison.