Re: [blink-dev] Re: Intent to Ship: HTTPS Upgrades

Fantastic, thanks for the update. Hope it sticks! -mike On Mon, Oct 16, 2023 at 20:15 Chris Thompson wrote: > We enabled HTTPS-Upgrades by default on trunk last week, and are currently > rolling out to 100% Stable. > > On Thu, Oct 5, 2023 at 10:42 AM Chris Thompson > wrote: > >> This week we i

Re: [blink-dev] Intent to Experiment: Compression dictionary transport with Shared Brotli

Hi, blink-dev We recently discovered a critical issue in the compression dictionary transport feature. As a result, we disabled the feature several days ago. This means that Origin Trial tokens for the feature will not work on the current Chrome Stable version. We have since fixed the bug and re-

[blink-dev] PSA: New baseline format for test-harness tests

Hi Blink Developers We want to let you know that we are in the process of converting baselines for test-harness tests into a new format. The reason is that we want to make baselines machine-parsable so that we can regenerate Wpt Metadata from Test Expectations and Baselines. We are doing this dir

Re: [blink-dev] Intent to Ship: WebGPU f16 support

Got it - thanks Chris. On Mon, Oct 16, 2023 at 4:54 PM Chris Harrelson wrote: > Hi, > > I don't think you need to do anything else. We'll re-review this intent at > our next meeting Wednesday morning PDT. > > The security review is already done >

Re: [blink-dev] Intent to Ship: WebGPU f16 support

Hi, I don't think you need to do anything else. We'll re-review this intent at our next meeting Wednesday morning PDT. The security review is already done and the other one is in progress. The API owners won't block on both finishing, we just wa

Re: [blink-dev] Intent to Ship: WebGPU f16 support

Blink API owners, could you please guide Ryan and Corentin on how to move this feature forward? Perhaps it's best to just have the privacy team sign off on it - this should be easy because there is no privacy concern for this feature. Again, while this is a medium-sized WebGPU shading language fe

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

LGTM1 On 10/15/23 11:07 AM, 'Sahir Vellani' via blink-dev wrote: Thanks for the feedback, I wasn't aware they were mandatory. The steps have been started, just awaiting feedback from Security and Privacy reviewers. I've received LGTMs for all other areas. After our response to WebKit's questio

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

LGTM1 On 10/16/23 7:48 AM, Nan Lin wrote: Thanks Mike, please see the inline comment. On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor wrote: Interoperability and Compatibility The change is backwards compatible, and allows developers to select the deployment option for t

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

On 10/16/23 7:57 AM, Nan Lin wrote: A few more inline comments, thanks! On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor wrote: Hi Nan, a few questions inline: On 10/6/23 8:45 AM, Nan Lin wrote: Contact emails lin...@chromium.org , jo

[blink-dev] BlinkOn 18 is tomorrow!

bcc: blink-dev@ and BlinkOn 18 attendees Hi all, BlinkOn 18 is tomorrow! If you’re still needing to register to attend virtually, do so here . Virtual registration will be open unti

Re: [blink-dev] Intent to Prototype: Verifying IPFS client

Thanks for posting this here. I have a couple questions/suggestions: * In your explainer, I don't see a description of the use cases for each of the 3 URL forms you plan to implement. https://tag.w3.org/explainers/ has some guidance around doing that. * The explainer says "Why HTTP(s)?", but nothi

[blink-dev] Intent to Ship: Fenced Frame - Functionality Updates

Contact emails shivani...@chromium.org d...@chromium.org jkar...@chromium.org lbr...@google.com Explainer(s) Send Automatic Beacons To All Registered Destinations https://github.com/WICG/turtledove/pull/808 Spec(s) Send Automatic Beacons To All Registered Destinations (Initial version) htt

[blink-dev] Intent to Prototype: Verifying IPFS client

*Contact emails* j...@littlebearlabs.io (primary) jfernan...@igalia.com dietr...@protocol.ai *Explainer* https://github.com/little-bear-labs/ipfs-chromium/blob/main/doc/explainer.md *Specification* Multiple specs are relevant. The most important is: https://specs.ipfs.tech/http-gateways/trustles

[blink-dev] PSA: Extra supported format for Protected Audience size macros

Hi blink-dev, PSA: In the Protected Audience API within the Privacy Sandbox, there is an opt-in feature that allows you to macro the size of the ad that wins the auction into the ad’s url, like: https://ad.com?width={%AD_WIDTH%}&height={%AD_HEIGHT%} (See https://github.com/WICG/turtledove/pull/

Re: [blink-dev] Intent to Re-implement and Ship: CSS Font Loading API - FontFaceSet: check() method

LGTM2 On 10/16/23 1:35 PM, Alex Russell wrote: LGTM1 On Sun, Oct 15, 2023 at 1:01 PM ChangSeok Oh wrote: Contact emails changseok...@bytedance.com,shivami...@gmail.com Specification https://drafts.csswg.org/css-font-loading/#font-face-set-check Summary The FontFaceS

Re: [blink-dev] Intent to Experiment: Web app scope extensions

In this case, I want to make sure there's enough time for app partners to enroll in January when M121 reaches Stable and for us to help them troubleshoot the configuration needed. This feature requires more server-side configuration ( of /.well-known/web-app-origin-association) that could take

Re: [blink-dev] Intent to Ship: Storage Access API with Prompts

We're now rolling this feature out to 100% on Chrome Stable (M117 and later). On Tuesday, September 26, 2023 at 11:20:29 AM UTC-4 Chris Fredrickson wrote: > Belatedly updating this thread in case folks are monitoring it -- we've > enabled this feature on 1% of Chrome Stable (M117) clients. We'l

Re: [blink-dev] Intent to Re-implement and Ship: CSS Font Loading API - FontFaceSet: check() method

LGTM1 On Sun, Oct 15, 2023 at 1:01 PM ChangSeok Oh wrote: > Contact emails > changseok...@bytedance.com, shivami...@gmail.com > > Specification > https://drafts.csswg.org/css-font-loading/#font-face-set-check > > Summary > > The FontFaceSet's check() function verifies whether it's possible to >

Re: [blink-dev] Intent to Prototype and Ship: URL.canParse

LGTM2 On Mon, Oct 16, 2023 at 7:24 AM Mike Taylor wrote: > LGTM1 > On 10/13/23 6:08 PM, Jeremy Roman wrote: > > Contact emails jbro...@chromium.org > > Explainer None > > Specification https://url.spec.whatwg.org/#dom-url-canparse > > Summary > > A static operation to determine whether a URL str

Re: [blink-dev] Intent to Experiment: Web app scope extensions

I'm supportive of this, but curious why 6 milestones. If there are partners signed up to provide feedback, can we summarize that input sooner than 6 months? Best, Alex On Mon, Oct 16, 2023 at 9:00 AM 'Lu Huang' via blink-dev < blink-dev@chromium.org> wrote: > Quick update: > We would like to pu

Re: [blink-dev] Intent to Experiment: Web app scope extensions

Quick update: We would like to push the start back to M121, and request that it run for 6 milestones initially. First milestone: 121. Last milestone: 126. On Thursday, October 12, 2023 at 10:11:29 AM UTC-7 mike...@chromium.org wrote: > Jason, could you please work with Lu to figure out why he

Re: [blink-dev] Intent to Ship: WebGPU f16 support

I cannot figure out how in the chromestatus entry how to set these reviews (privacy & security) as being 'N/A'. The only entries related to these that appear in 'Edit All Fields' are up in the dev trial section, and changing those values, don't appear to affect the chips. Clicking on the chips for

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

A few more inline comments, thanks! On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor wrote: > Hi Nan, a few questions inline: > On 10/6/23 8:45 AM, Nan Lin wrote: > > Contact emails > > lin...@chromium.org, johni...@chromium.org > > Explainer > > Attribution Reporting with event-level reports >

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

Thanks Mike, please see the inline comment. On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor wrote: > Hi Nan, a few questions inline: > On 10/6/23 8:45 AM, Nan Lin wrote: > > Contact emails > > lin...@chromium.org, johni...@chromium.org > > Explainer > > Attribution Reporting with event-level report

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

Hi Nan, a few questions inline: On 10/6/23 8:45 AM, Nan Lin wrote: Contact emails lin...@chromium.org , johni...@chromium.org Explainer Attribution Reporting with event-level reports

Re: [blink-dev] Intent to Prototype and Ship: URL.canParse

LGTM1 On 10/13/23 6:08 PM, Jeremy Roman wrote: Contact emails jbro...@chromium.org Explainer None Specification https://url.spec.whatwg.org/#dom-url-canparse Summary A static operation to determine whether a URL string is valid. More concise than catc

Re: [blink-dev] Intent to Experiment: 'priority' HTTP request header

Issue has been filed with the whatwg spec to specify the behavior of the priority header, either by adding it to the forbidden header list or by defining how the networking layer should behave if there is an application-supplied value. On Wed, Oct 11,

Re: [blink-dev] Intent to Experiment: Unrestricted access to performance.measureUserAgentSpecificMemory()

On Fri, Oct 13, 2023 at 3:58 PM Michael Lippautz wrote: > Thanks! > > On Fri, Oct 13, 2023 at 10:52 AM Yoav Weiss > wrote: > >> This is exciting! Thanks for working on this!! >> >> On Fri, Oct 13, 2023 at 10:42 AM Michael Lippautz >> wrote: >> >>> Contact emails >>> >>> v...@chromium.org, mlipp

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

Hi Grzegorz, HTTP/2 server push was disabled by default in Chrome 106[1]. You can achieve the almost the same latency speedup via preloading and prerendering (rel=preload [2] and rel=prerender) and HTTP Early Hints[3] (supported since Chrome 103) and speculation rules. [1] https://developer.ch