Re: [blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

Hi Thomas, I'm part of the team working on Early Hints. On Wed, Mar 16, 2022 at 6:58 AM BIANCONI Thomas wrote: > I am sad to read this... > A new step before the deprecation of server push. > > I would love to see comparaison in term of performance between server push > and early hint. > On a p

RE: [blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

I am sad to read this... A new step before the deprecation of server push. I would love to see comparaison in term of performance between server push and early hint. On a pure theoric point of view early hint starts during the html parsing whereas the server push start with the response header.

Re: [blink-dev] Intent to Prototype + Ship: Secure Payment Confirmation API V3

On 3/15/22 4:42 PM, Nick Burris wrote: On Tue, Mar 15, 2022 at 4:52 PM Mike Taylor wrote: On 3/9/22 10:27 AM, Nick Burris wrote: Contact emails nbur...@chromium.org, rous...@chromium.org, smcgr...@chromium.org, ma...@chromium.org Explainer https:/

[blink-dev] Re: Intent to Prototype: CSS object-view-box and object-overflow

On Tue, Mar 15, 2022 at 9:11 AM Camille Lamy wrote: > We looked at this as part of the Security & privacy review process for Web > Platform intents, and we were wondering about the feature behavior with > regards to iframes. Specifically, we were concerned about the potential for a > child fram

Re: [blink-dev] Intent to Prototype + Ship: Secure Payment Confirmation API V3

On Tue, Mar 15, 2022 at 4:52 PM Mike Taylor wrote: > On 3/9/22 10:27 AM, Nick Burris wrote: > > Contact emails > > nbur...@chromium.org, rous...@chromium.org, smcgr...@chromium.org, > ma...@chromium.org > > Explainer > > https://github.com/w3c/secure-payment-confirmation/blob/main/explainer.md >

Re: [blink-dev] Intent to Prototype + Ship: Secure Payment Confirmation API V3

On 3/9/22 10:27 AM, Nick Burris wrote: Contact emails nbur...@chromium.org, rous...@chromium.org, smcgr...@chromium.org, ma...@chromium.org Explainer https://github.com/w3c/secure-payment-confirmation/blob/main/explainer.md

Re: [blink-dev] Intent to Ship: Add Save Data Client Hint

(1) Can we omit the header when the value would be `?0` (false)? I'm fine with that, and it would be worth updating the existing client hint standard to allow the conflation of empty/missing values in cases where headers are sent by default. It's not worth the bytes to clarify the header is empty,

Re: [blink-dev] Re: Intent to Ship: MediaCapabilities API for WebRTC

On Tue, Mar 15, 2022 at 5:38 PM jmedley via Chromestatus < admin+jmed...@cr-status.appspotmail.com> wrote: > In which version are you hoping to ship? > All code has landed except a few minor tweaks that I'm currently working on so my goal is to ship this in M101. Do you think that's reasonable?

Re: [blink-dev] Re: Intent to Prototype and Ship: font-palette and custom @font-palette-values palettes

LGTM3. -mike On Tue, Mar 15, 2022 at 5:12 PM Mike Taylor wrote: > LGTM2 > > On 3/15/22 11:20 AM, Yoav Weiss wrote: > > LGTM1 - given the early positive signal and the fact it's already shipping > in Safari. Please follow up on any feedback from others if it comes up on > that thread. > > On Tu

Re: [blink-dev] Intent to Ship: Add Save Data Client Hint

Hey Avi! Two questions, one small, one large: First, to reduce header bloat, the approach of not sending headers by default whose value is `?0` seems reasonable. Fetch Metadata's `Sec-Fetch-User` header is a good example of this. Can

[blink-dev] Re: Intent to Ship: MediaCapabilities API for WebRTC

In which version are you hoping to ship? -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visi

Re: [blink-dev] Re: Intent to Prototype and Ship: font-palette and custom @font-palette-values palettes

LGTM2 On 3/15/22 11:20 AM, Yoav Weiss wrote: LGTM1 - given the early positive signal and the fact it's already shipping in Safari. Please follow up on any feedback from others if it comes up on that thread. On Tue, Mar 15, 2022 at 3:27 PM Dominik Röttsches wrote: Hi again Yoav and oth

[blink-dev] Re: Intent to Prototype: CSS object-view-box and object-overflow

Hi! We looked at this as part of the Security & privacy review process for Web Platform intents, and we were wondering about the feature behavior with regards to iframes. Specifically, we were concerned about the potential for a child frame to draw custom content over its parent using this feat

[blink-dev] Re: Intent to Prototype and Ship: font-palette and custom @font-palette-values palettes

LGTM1 - given the early positive signal and the fact it's already shipping in Safari. Please follow up on any feedback from others if it comes up on that thread. On Tue, Mar 15, 2022 at 3:27 PM Dominik Röttsches wrote: > Hi again Yoav and others, > > On Mon, Mar 14, 2022 at 5:18 PM Dominik Rötts

[blink-dev] Re: Intent to Prototype and Ship: font-palette and custom @font-palette-values palettes

Hi again Yoav and others, On Mon, Mar 14, 2022 at 5:18 PM Dominik Röttsches wrote: > Hi Yoav, > > On Thursday, March 10, 2022 at 9:18:17 AM UTC+2 yoav...@chromium.org > wrote: > >> Thanks for working on this! Seems like a very cool feature!! :) >> >> On Tuesday, March 8, 2022 at 1:44:55 PM UTC+1

Re: [blink-dev] Intent to Ship: Omnibox Prerendering

Hi, While we are discussing, we would like to continue the incremental roll out of the feature to non-Stable channels. As of now, we are testing out the feature on 60% of Dev/Canary channels, and 60% of Beta channels. The rollout is limited to Android Chrome (limitation of the current implementati

Re: [blink-dev] Intent to Ship: MediaCapabilities API for WebRTC

On Tue, Mar 15, 2022 at 9:22 AM Johannes Kron wrote: > Thank you Mike and Yoav for your feedback! > > I accidentally responded with Reply to sender instead of Reply all. Trying > again, see my response below. > > > On Mon, Mar 14, 2022 at 6:33 PM Mike Taylor > wrote: > >> On 3/14/22 1:30 PM, 'Jo

Re: [blink-dev] Intent to Ship: MediaCapabilities API for WebRTC

Thank you Mike and Yoav for your feedback! I accidentally responded with Reply to sender instead of Reply all. Trying again, see my response below. On Mon, Mar 14, 2022 at 6:33 PM Mike Taylor wrote: > On 3/14/22 1:30 PM, 'Johannes Kron' via blink-dev wrote: > > Risks > > > Interoperability and