246508 2022-10-14 00:58:42 -0700 Implement Fetch Metadata Request Headers (aka Sec-Fetch-*) 2023-03-02 13:58:53 -0800 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=247696 https://w3c.github.io/webappsec-fetch-metadata/ InRadar P2 Normal --- 204744 237550 238265 253265 1 annevk pgriffis pgriffis webkit-bug-importer oldest_to_newest 1905556 0 annevk 2022-10-14 00:58:42 -0700 This is a tracking bug for the various dedicated Fetch Metadata bugs. Seems all headers apart from Sec-Fetch-Site and Sec-Fetch-User are covered thus far, but Sec-Fetch-Site has a patch. 1905557 1 webkit-bug-importer 2022-10-14 00:58:54 -0700 <rdar://problem/101162929> 1907312 2 pgriffis 2022-10-21 08:55:06 -0700 I don't plan on working on Sec-Fetch-User, at least for now. Discussing it with some people from Google they said that User wasn't very reliable nor the most important of them. It should be doable in WebKit but it seemed less straightforward that Chromium which has more direct access to the browser UI layers to track user actions. I'd like to see the current work that is done at least move to be enabled as an experimental feature. 1910807 3 pgriffis 2022-11-07 09:51:49 -0800 Pull request: https://github.com/WebKit/WebKit/pull/6211 1911053 4 ews-feeder 2022-11-08 11:44:53 -0800 Committed 256456@main (cb60df93ab8c): <https://commits.webkit.org/256456@main> Reviewed commits have been landed. Closing PR #6211 and removing active labels. 1911204 5 annevk 2022-11-09 02:14:47 -0800 Patrick, this wasn't meant to be the "enable by default" bug. Now we have nothing open to track the remaining WebSocket-related issue as well as Sec-Fetch-User. Could you file a new tracking bug perhaps as I guess we cannot reopen this one now it's associated with that PR? 1911354 6 pgriffis 2022-11-09 13:52:50 -0800 Sorry about that. I opened https://bugs.webkit.org/show_bug.cgi?id=247696