Re: [webkit-dev] Request for Position: Fetch Metadata

2022-02-22 Thread youenn fablet via webkit-dev
I also think this is worth prototyping. Destination and mode are valuable and are hopefully not controversial, I would start with those two. I would also hope WPT coverage is good in that area and would cover both regular network loads as well as cache loads. Not sure how this would play with memor

Re: [webkit-dev] Request for Position: Fetch Metadata

2022-02-21 Thread Alex Christensen via webkit-dev
I’m interested in this work, and would be happy to review patches. I noticed that Chrome and Firefox both implement it and we don’t. Some of the implementation might be a little involved, so I’m happy to answer questions and point in the right direction when I can. I’m not thrilled that it ad

Re: [webkit-dev] Request for Position: Fetch Metadata

2022-02-16 Thread Patrick Griffis via webkit-dev
On 2022-02-11 16:15, Patrick Griffis via webkit-dev wrote: > However Sec-Fetch-User I believe will require more > significant changes that will have to be exposed to each port. It > requires knowing if a request was initiated by a user, exact details are > specified here[2], which I think will requ

[webkit-dev] Request for Position: Fetch Metadata

2022-02-11 Thread Patrick Griffis via webkit-dev
Hi everybody, I'd like a position on the Fetch Metadata[0] spec. It is a security feature that provides extra context to fetch requests so that servers can make informed decisions. It is currently implemented by both Firefox and Chromium. I have started a work-in-progress patch[1] on bug 204744 f