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

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

Thanks for sharing this with us.  Aside from @torgo's comment about explainers and user needs (which are indirect for this API generally, but still worth writing down), the feature is worthwhile.  Compression encoding in particular has a material effect on performance and being able to split performance reports by the choice of encoding makes a lot of sense.  We don't see any other major problems.

A couple of notes about your security and privacy questionnaire: 

1. You answered negatively about question 7 (information about the browser platform), which is incorrect.  It reveals which content codings are supported by the browser.  This is acceptable because that information is already exposed through other means and - more importantly - it is browser-specific rather than user-specific.  You include this in your analysis already, but it's worth getting the questionnaire correct.
2. Question 21 saying "not directly" is troubling.  I can't see how this would reveal anything about the use of assistive technology.  If it does, that would be cause for concern and some further analysis.  Can you say more?

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

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