search

WebKit / standards-positions

WebKit's positions on emerging web specifications
https://webkit.org/standards-positions/
254 stars 21 forks source link

User Agent Client Hints #70

Open gsnedders opened 2 years ago

gsnedders commented 2 years ago

Request for position on an emerging web specification

Information about the spec

Design reviews and vendor positions

See also https://mozilla.github.io/standards-positions/#ua-client-hints.

Bugs tracking this feature

Anything else we need to know

This builds on top of the infrastructure defined in #20. We've filed a variety of issues on both UA Client Hints and the infrastructure specs previously, but the only one that I believe is still open is https://github.com/WICG/ua-client-hints/issues/151.

othermaciej commented 2 years ago

I think a resolution to https://github.com/WICG/ua-client-hints/issues/151 is still important (I need to go back and look at what it says). Also need to look at the dependencies to ensure the base UA Client Hints spec doesn't effectively mandate implementing all client hints for browsers that implementing.

othermaciej commented 2 years ago

The privacy concerns are due to the unresolved issue, and for additional close reading by privacy experts.

The interoperability concerns are because the spec allows a wide range of more or less privacy protective behaviors (with resolutions to privacy issues often being to add a MAY rather than to change the required behavior), and it's possible sites may come to depend on behaviors that aren't required by the spec.

miketaylr commented 2 years ago

I'd be very happy to work with someone in the WebKit project to address the open concerns (and if there was interest to implement, we could move this out of WICG into something like webapps WG to make collaboration simpler).

litherum commented 1 year ago

What's the difference between this and https://github.com/WebKit/standards-positions/issues/20?

gsnedders commented 1 year ago

What's the difference between this and #20?

See the comments on #20: #20 is about client hint general infrastructure, this is about the UA client hints, there are other issues filed for positions on other client hints.

othermaciej commented 1 year ago

Besides the earlier cited issue, I think this one was not actually addressed in a satisfactory way (I can’t figure out how to reopen it in GitHub) https://github.com/WICG/ua-client-hints/issues/146

hober commented 1 year ago

We need to come to a position on https://github.com/WebKit/standards-positions/issues/20 before we can come to positions on proposals that use the Client Hints infrastructure.

miketaylr commented 1 year ago

I think this one was not actually addressed in a satisfactory way (I can’t figure out how to reopen it in GitHub) WICG/ua-client-hints#146

Thanks, I've re-opened it.

djmitche commented 9 months ago

FYI, this Chrome feature tracks adding Sec-CH-UA-Form-Factor to UA Client Hints. I don't think this particular hint moves the needle on the overall position on client hints, but I'm happy to learn more.