Re: [w3ctag/design-reviews] User Preference Media Features Client Hints Headers (#632)

> @tomayac @beaufortfrancois I'm fairly sure the current co-chair of the CSSWG is well aware of how to apply media queries to a stylesheet (as is this former co-chair of the CSSWG).

No doubt you all are aware, it was purely in response to _"the user will experience unexpected effects because rules from the two stylesheets will co-exist"_.
 
> The point we're trying to make is: while it's certainly possible to use media feature client hints in a way that doesn't break user experience, there are many ways that it can be used that _can_. And those ways seems to be more likely to be employed by those without a deep understanding of what they're doing.

Not sure where the argument is headed; are you saying someone knowledgable enough to work with HTTP headers would then at the same time not be knowledgable enough to work with CSS, as in the back-end/front-end divide? If so, yes, this might be the case. In our [communication](https://web.dev/user-preference-media-features-headers/) we have positioned the feature as aimed at sites of the scale of `google.com`, but definitely not the average website.

> This feature seems like a giant foot-gun that only serves to shave a few bytes off the wire. We're questioning if the gains outweigh the risks.

On the Google Search team we were trying to make the case that it's not just _"a few bytes"_, plus that for high traffic volume sites like `google.com` every byte does make a difference. Again, this is not aimed at the average website. Maybe we should make this even clearer!?



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

Received on Wednesday, 29 September 2021 08:38:34 UTC