Kagami Sascha Rosylight

Merge a PR only with explicit implementor consensus (followup)

4

See the discussion in https://github.com/w3c/clipboard-apis/pull/197#issuecomment-1841380176. It has Agenda+ but in a closed PR, so I'm opening a new issue to make things a bit more clear.

Remove clipboard-write permission

14

Closes #163 For normative changes, the following tasks have been completed: * [x] Modified Web platform tests (link to pull request) (Already marked as tentative, no need to change) Implementation...

Icon fetch in Gecko/Blink uses document charset for URL encoding

3

### What is the issue with the Notifications API Standard? Part of #208 and #5. Just found that Both Firefox and Chrome depends on [the legacy URL encoding behavior](https://html.spec.whatwg.org/multipage/urls-and-fetching.html#encoding-parsing-a-url), while...

### What is the issue with the Notifications API Standard? https://notifications.spec.whatwg.org/#resources >If the notification platform supports images, [fetch](https://fetch.spec.whatwg.org/#concept-fetch) notification’s [image URL](https://notifications.spec.whatwg.org/#image-url), if [image URL](https://notifications.spec.whatwg.org/#image-url) is set. But the fetch algorithm...

Permission check happens first on both Gecko and Blink for showNotification

5

### What is the issue with the Notifications API Standard? The current spec in https://notifications.spec.whatwg.org/#dom-serviceworkerregistration-shownotification creates a notification in step 5 and do the permission check in step 6 where...

AFAIK WPT does not shuts the process down after a crashtest, and I've seen many cases in Mozilla where we opted not to write WPT solely because of that. Could...

New standard: Compression Streams

4

Following https://github.com/WICG/compression/issues/32, I propose standardizing Compression Streams API in WHATWG. It's an API that allows compressing and decompressing BufferSource types using a set of the most common compression algorithms (gzip/deflate/deflate-raw)...

Discourage use of insecure HTTP for client_id and redirect_uri?

3

Per https://indieauth.spec.indieweb.org/#client-identifier: >Client identifier URLs MUST have either an https or http scheme But the spec does not discourage the latter, nor whether the server may reject the latter, and...

Require explicitly specifying `redirect_uri` instead of allowing same-host URIs by default?

1

[Section 4.2.2](https://indieauth.spec.indieweb.org/#redirect-url) says: >If a client wishes to use a redirect URL that has a different host than their client_id, or if the redirect URL uses a custom scheme (such...

昔のリンクがまだありましたので