Re: [w3ctag/design-reviews] Expose contentEncoding in resourceTiming (Issue #1064)

martinthomson left a comment (w3ctag/design-reviews#1064)

Is there any reason not to include the value of the header?  Why is this being mutated this way?  Is the concern that this could encode a cookie or something like that?  Isn't that something that you can do with the URL anyway?

(This is a list of tokens, so it should probably be a JSON array of strings.)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1064#issuecomment-2937858608
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1064/2937858608@github.com>

Received on Wednesday, 4 June 2025 00:27:34 UTC