Anchor permanence for integration with compression dictionary spec?

[pmeenan]

What is the issue with the Fetch Standard?

As per https://whatwg.org/working-mode#anchors could we please make the following anchors permanent?

• https://fetch.spec.whatwg.org/#concept-request-destination
• https://fetch.spec.whatwg.org/#cors-check

These are used by the compression dictionary IETF spec.

[domenic]

I think https://fetch.spec.whatwg.org/#concept-request-destination might be better than the enum?

Anyway let's remember to use https://speced.github.io/bikeshed/#metadata-required-ids to enforce this.

[pmeenan]

Thanks. I'll update the draft to use concept-request-destination instead.

[annevk]

When will Compression Dictionary be more properly integrated with Fetch? It seems this could be done as part of that.

[pmeenan]

I'm starting to work on a PR now. I can include the chance as part of the PR if we think we will be able to land the integration based on browser interest and without a second implementation.

…

On Thu, Aug 29, 2024 at 2:31 AM Anne van Kesteren ***@***.***> wrote: When will Compression Dictionary be more properly integrated with Fetch? It seems this could be done as part of that. — Reply to this email directly, view it on GitHub <#1771 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADMOBLQEEV2WQ4MHRPOVF3ZT253RAVCNFSM6AAAAABNIW7B7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWHAYTGNZUGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[annevk]

Our process does not require two implementations. See https://whatwg.org/working-mode#changes.