Re: [blink-dev] Intent to Ship: fetch() upload streaming

On Wed, Jul 13, 2022 at 7:23 PM Yoav Weiss wrote: > > > On Monday, July 11, 2022 at 12:50:11 PM UTC+2 Yutaka Hirano wrote: > >> On Mon, Jul 11, 2022 at 7:41 PM Yutaka Hirano >> wrote: >> >>> >>> >>> On Mon, Jul 11, 2022 at 5:41 PM Yoav

Re: [blink-dev] Intent to Ship: fetch() upload streaming

On Mon, Jul 11, 2022 at 7:41 PM Yutaka Hirano wrote: > > > On Mon, Jul 11, 2022 at 5:41 PM Yoav Weiss wrote: > >> >> >> On Mon, Jul 11, 2022 at 10:17 AM Yutaka Hirano >> wrote: >> >>> Contact emailsyhir...@chromium.org >>> &g

Re: [blink-dev] Intent to Ship: fetch() upload streaming

On Mon, Jul 11, 2022 at 5:41 PM Yoav Weiss wrote: > > > On Mon, Jul 11, 2022 at 10:17 AM Yutaka Hirano > wrote: > >> Contact emailsyhir...@chromium.org >> >> Explainerhttps://bit.ly/2SVvKbR >> >> Specificationhttps://fetch.spec.whatwg.org/#concept-b

[blink-dev] Intent to Ship: fetch() upload streaming

Contact emailsyhir...@chromium.org Explainerhttps://bit.ly/2SVvKbR Specificationhttps://fetch.spec.whatwg.org/#concept-body-stream Design docs http://bit.ly/3asqra2 Summary Fetch upload streaming lets web developers make a fetch with a ReadableStream body. Fetch provides a generic definition o

Re: [blink-dev] Intent to Ship: "deflate-raw" on compression and decompression streams

On Sat, May 7, 2022 at 8:24 AM Mike Taylor wrote: > On 5/6/22 8:10 AM, Yutaka Hirano wrote: > > Contact emails > > yhir...@chromium.org > > Explainer > > None > > Specification > > https://wicg.github.io/compression/ > > https://github.com/wicg/compr

[blink-dev] Intent to Ship: "deflate-raw" on compression and decompression streams

Contact emails yhir...@chromium.org Explainer None Specification https://wicg.github.io/compression/ https://github.com/wicg/compression/pull/43 (spec PR) https://chromium-review.googlesource.com/c/chromium/src/+/3586945 (impl and tests) Summary Add a new compression format, "deflate-raw",

[blink-dev] Intent to Prototype: "deflate-raw" compression format

Contact emailsyhir...@chromium.org, ri...@chromium.org ExplainerNone Specificationhttps://wicg.github.io/compression/ https://github.com/WICG/compression/pull/43 Summary Add a new compression format, "deflate-raw", to give web developers to access to the raw deflate stream without any headers o

Re: [blink-dev] Intent to Extend Origin Trial: QuicTransport

cc;l=66;drc=ae97629737a9f0935c79337f5adb9b75e6edb84b > Thanks, > > Le 08/02/2021 à 14:38, 'Yutaka Hirano' via blink-dev a écrit : > > Please see > https://groups.google.com/a/chromium.org/g/blink-api-owners-discuss/c/uoQG64TjVcU > for the previous discussion. >

Re: [blink-dev] Re: Intent to extend the origin trial: WebTransport over HTTP/3

> thanks > > On Wednesday, October 27, 2021 at 10:34:56 PM UTC-7 Yutaka Hirano wrote: > >> On Thu, Oct 28, 2021 at 2:38 AM Joe Medley wrote: >> >>> Hi, >>> >>> Can I get some clarification? >>> >>> So this extends the origin tria

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

ges as well, so won't necessarily help with cases of existing > content, but may help to move newer auth flows to make safer CORS choices. > > Cheers :) > Yoav > > On Thursday, December 9, 2021 at 12:17:40 PM UTC+1 Yutaka Hirano wrote: > >> We've been showing a

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

point where > we can reasonably remove it. If it doesn't, we might need to do some more > research (wiring this counter up to UKM, for instance) to see if we can > track down more clear sources of potential breakage. > > -mike > > On Thursday, December 2, 2021 at 6:56:40 A

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

On Thu, Dec 2, 2021 at 12:29 AM Yoav Weiss wrote: > > > On Wed, Dec 1, 2021 at 4:00 PM Yutaka Hirano wrote: > >> Sorry for the delay! >> >> I checked 10 sites. I saw console errors in three sites among them: >> 1. https://cchatty.com/ >> 2. https://

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

> Would it be feasible to get a random list of 10-20 sites that hit the use >> counter and see if they are broken badly by this feature? >> >> On Thu, Nov 4, 2021 at 4:54 AM Yutaka Hirano >> wrote: >> >>> (friendly ping) >>> >>> On Mon,

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

(friendly ping) On Mon, Nov 1, 2021 at 1:57 PM Yutaka Hirano wrote: > Thank you for the feedback. > > Do you have concrete steps for the investigation in your mind? > > On Fri, Oct 29, 2021 at 4:30 AM Mike West wrote: > >> I think it's reasonable for us to dig

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

user-facing > breakage. Yutaka, is that something you'd be willing to dig into? > > The direction seems philosophically correct to me, so I'd like to see it > ship, but I'd also like to make sure we're not making the web worse for > users by doing so. > > -mike

Re: [blink-dev] Re: Intent to extend the origin trial: WebTransport over HTTP/3

is >>> slightly longer than usual. Given the evidence >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/kwC5wES3I4c/m/2WxYhllhAAAJ?utm_medium=email&utm_source=footer> >>> of >>> developer feedback presented in the I2S, that seems like a reas

Re: [blink-dev] Intent to Ship: CORS non-wildcard request-header

On Thu, Oct 21, 2021 at 6:25 PM Yoav Weiss wrote: > > > On Thu, Oct 21, 2021 at 9:55 AM Yutaka Hirano > wrote: > >> (The implementation CL >> <https://chromium-review.googlesource.com/c/chromium/src/+/3226283> is >> under review. This intent is wr

[blink-dev] Intent to Ship: CORS non-wildcard request-header

(The implementation CL is under review. This intent is written as if it's landed.) Contact emailsyhir...@chromium.org Specification https://fetch.spec.whatwg.org/#cors-non-wildcard-request-header-name Summary A CORS non-wildcar

[blink-dev] Intent to extend the origin trial: WebTransport over HTTP/3

Contact emails yhir...@chromium.org,vasi...@chromium.org Explainer https://github.com/w3c/webtransport/blob/main/explainer.md Design docs/spec Specification: https://w3c.github.io/webtransport/#web-transport https://docs.google.com/document/d/1UgviRBnZkMUq4OKcsAJvIQFX6UCXeCbOtX_wMgwD_es/edit

Re: [blink-dev] Intent to Ship: WebTransport

e. On Tue, Oct 12, 2021 at 3:53 PM Yutaka Hirano wrote: > Thank you! We'll land the shipping CL > <https://chromium-review.googlesource.com/c/chromium/src/+/3208466> after > addressing TAG review comments. > > On Sat, Oct 9, 2021 at 1:07 AM Rick Byers wrote: > &g

Re: [blink-dev] Intent to Ship: WebTransport

t;> think we ought to block on. >>> >>> I'll also note that the TAG just put this on their agenda for this >>> coming week. If concerns are raised there, I would appreciate us addressing >>> them thoroughly before shipping. >>> >>> -mike >&g

Re: [blink-dev] Intent to Ship: WebTransport

On Thu, Oct 7, 2021 at 5:51 PM Yutaka Hirano wrote: > > > On Thu, Oct 7, 2021 at 5:38 PM Philip Jägenstedt > wrote: > >> On Thu, Oct 7, 2021 at 10:04 AM Yutaka Hirano >> wrote: >> >>> Thank you! >>> >>> On Thu, Oct 7, 2021 at 4:45 P

Re: [blink-dev] Intent to Ship: WebTransport

On Thu, Oct 7, 2021 at 5:38 PM Philip Jägenstedt wrote: > On Thu, Oct 7, 2021 at 10:04 AM Yutaka Hirano > wrote: > >> Thank you! >> >> On Thu, Oct 7, 2021 at 4:45 PM Philip Jägenstedt >> wrote: >> >>> On Tue, Oct 5, 2021 at 3:20 PM Yutaka Hir

Re: [blink-dev] Intent to Ship: WebTransport

Thank you! On Thu, Oct 7, 2021 at 4:45 PM Philip Jägenstedt wrote: > On Tue, Oct 5, 2021 at 3:20 PM Yutaka Hirano wrote: > >> >> >> On Mon, Oct 4, 2021 at 10:04 PM Philip Jägenstedt >> wrote: >> >>> On Fri, Oct 1, 2021 at 9:27 PM Yutaka Hirano &

Re: [blink-dev] Intent to Ship: WebTransport

On Tue, Oct 5, 2021 at 10:20 PM Yutaka Hirano wrote: > > > On Mon, Oct 4, 2021 at 10:04 PM Philip Jägenstedt > wrote: > >> On Fri, Oct 1, 2021 at 9:27 PM Yutaka Hirano >> wrote: >> >>> Hi Philip, >>> >>> Sorry for the belated repl

Re: [blink-dev] Intent to Ship: WebTransport

On Mon, Oct 4, 2021 at 10:04 PM Philip Jägenstedt wrote: > On Fri, Oct 1, 2021 at 9:27 PM Yutaka Hirano wrote: > >> Hi Philip, >> >> Sorry for the belated reply. Comments inline: >> >> On Thu, Sep 30, 2021 at 7:31 PM Philip Jägenstedt >> wrote: >>

Re: [blink-dev] Intent to Ship: WebTransport

On Mon, Oct 4, 2021 at 3:49 PM Yang Guo wrote: > Thank you for thinking about debuggability! I understand the rationale > behind not providing more details. Would it make sense though to link to > chrome://net-export from DevTools' Network Panel? > > Actually after implementing the minimal suppor

Re: [blink-dev] Intent to Ship: WebTransport

things > need to block that, and what things can be left until later. > > Comments inline... > > On Mon, Sep 27, 2021 at 6:55 AM Yutaka Hirano > wrote: > >> Contact emails >> >> yhir...@chromium.org, vasi...@chromium.org >> >> Explainer >> &g

Re: [blink-dev] Intent to Ship: WebTransport

29, 2021 at 11:25 PM Philip Jägenstedt wrote: > On Wed, Sep 29, 2021 at 12:32 PM Yutaka Hirano > wrote: > >> Hi Philip, >> >> On Wed, Sep 29, 2021 at 6:29 PM Philip Jägenstedt >> wrote: >> >>> Hi Yutaka, >>> >>> This is a big n

Re: [blink-dev] Intent to Ship: WebTransport

s after shipping the >> feature would carry compatibility risks. >> >> On Sun, Sep 26, 2021 at 9:55 PM Yutaka Hirano >> wrote: >> >>> Contact emails >>> >>> yhir...@chromium.org, vasi...@chromium.org >>> >>> Exp

[blink-dev] Intent to Ship: WebTransport

Contact emails yhir...@chromium.org, vasi...@chromium.org Explainer https://github.com/w3c/webtransport/blob/main/explainer.md Specification https://w3c.github.io/webtransport https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3/ https://datatracker.ietf.org/doc/html/draft-ietf-qu

Re: [blink-dev] Re: Native support of Windows SSO in Chrome

I have some questions. - Is the proposal that Chrome detects such a redirect and sends an authentication request to IDP? - Is there at most one IDP for a profile? - How is IDP registered to Chrome? Thanks, On Fri, Sep 24, 2021 at 6:18 AM Owen Min wrote: > +people who may be interested in th

Re: [blink-dev] Intent to Implement and Ship: WritableStream controller AbortSignal

On Thu, Sep 2, 2021 at 12:22 PM Nidhi Jaju wrote: > > > On Wed, Sep 1, 2021 at 10:54 PM Alex Russell > wrote: > >> Incremental features often benefit from TAG guidance. I'd feel better if >> this intent at least cited prior TAG reviews in this area or filed an FYI >> (with potential for TAG to r