Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Done. ~ Ari Chivukula (Their/There/They're) On Fri, Oct 27, 2023 at 5:25 PM Chris Harrelson wrote: > Can you please also fill out the *Goals for experimentation* section? > > On Thu, Oct 26, 2023 at 8:21 AM Ari Chivukula > wrote: > >> Contact emails >> >> aric...@chromium.org, wanderv...@chro

[blink-dev] Intent to Prototype: WebAuthn related origins

*Contact emails* a...@chromium.org *Explainer* https://github.com/w3c/webauthn/wiki/Explainer:-Related-origin-requests *Summary* All WebAuthn credentials are associated with a single Relying Party ID (“RP ID”), which is essentially a domain name, and all WebAuthn requests are processed in the con

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

I have a website that needs to receive "Header Enrichment" over HTTP, which reads the MSISDN when the user browses via their mobile data. Previously, the user accessed via HTTPS, and we would switch to HTTP to perform the "Header Enrichment" reading and then switch back to HTTPS. With this upda

Re: [blink-dev] Intent to Ship: Private Aggregation API: aggregation coordinator selection

LGTM2 On 10/27/23 5:13 PM, Chris Harrelson wrote: LGTM1 On Fri, Oct 20, 2023 at 9:44 AM Alex Turner wrote: Contact emails ale...@chromium.org Explainer https://github.com/patcg-individual-drafts/private-aggregation-api#aggregation-coordinator-cho

Re: [blink-dev] Re: Intent to Ship: FedCM extensions: Error API and Auto-Selected Flag API

However, even for WHATWG specs we have in the past blocked approval until spec PRs landed in cases where the only blocker was editorial review. This appears to be a similar situation. On Fri, Oct 27, 2023 at 2:17 PM Rick Byers wrote: > FedCM has decided to follow a WHATWG-like working mode >

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Can you please also fill out the *Goals for experimentation* section? On Thu, Oct 26, 2023 at 8:21 AM Ari Chivukula wrote: > Contact emails > > aric...@chromium.org, wanderv...@chromium.org, johann...@chromium.org, > hele...@google.com > > > Specification > > https://arichiv.github.io/saa-non-co

Re: [blink-dev] Re: Intent to Ship: FedCM extensions: Error API and Auto-Selected Flag API

FedCM has decided to follow a WHATWG-like working mode where normative PRs land only with 2+ implementer support. Given that reviews were requested almost 2 months ago, and the blink launch process is designed not to stall indefinitely on consensus, I d

Re: [blink-dev] Intent to Ship: Array.fromAsync

LGTM3 On Thu, Oct 26, 2023 at 4:04 PM Johnny Stenback wrote: > +1 to what Chris said. And if you feel a gate doesn't apply, you can state > in a comment that you believe the result of the review should be n/a. And > we're in fact in the midst of landing a short-hand button that does that > for a

Re: [blink-dev] Intent to Ship: Private Aggregation API: aggregation coordinator selection

LGTM1 On Fri, Oct 20, 2023 at 9:44 AM Alex Turner wrote: > Contact emails > > ale...@chromium.org > > Explainer > https://github.com/patcg-individual-drafts/private-aggregation-api#aggregation-coordinator-choice > Specification > https://github.com/patcg-individual-drafts/private-aggregation-api

Re: [blink-dev] Intent to Ship: WebGPU on Android

Thanks! It was unclear what the procedure was here since this isn't a new feature, just enabling it on a new platform. I'll make sure they are updated appropriately. --Brandon On Fri, Oct 27, 2023 at 2:04 PM Chris Harrelson wrote: > > > On Fri, Oct 27, 2023 at 1:57 PM Mike Taylor > wrote: > >>

Re: [blink-dev] Intent to Ship: WebGPU on Android

On Fri, Oct 27, 2023 at 1:57 PM Mike Taylor wrote: > LGTM2 % requesting all of the review gates in the chromestatus entry. > Ah yes - please do start those reviews. Likely you can mark them as N/A because this is just shipping an existing API on a new platform. > On 10/27/23 4:25 PM, Chris Harr

Re: [blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

Hi Mustaq, "web developer facing change to existing code" is meant for "bugfix-level changes to web APIs", which is why it only requires a PSA (sorry for the confusion - this has been a common issue and the chromestatus team is working on improved UI to be less confusing). In your case you are ma

Re: [blink-dev] Intent to Ship: WebGPU on Android

LGTM2 % requesting all of the review gates in the chromestatus entry. On 10/27/23 4:25 PM, Chris Harrelson wrote: LGTM1 - this is an easy one :) On Fri, Oct 27, 2023 at 1:21 PM 'Brandon Jones' via blink-dev wrote: Contact emails bajo...@chromium.org, cwal...@chromium.org

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

LGTM3. (I verified off-list that the temporary navigator.cookieDeprecationLabel API will indeed not be exposed to all users, so I feel pretty confident and the low burn-in risks.) On 10/27/23 4:51 PM, Chris Harrelson wrote: LGTM2! On Fri, Oct 27, 2023 at 1:50 PM Ben Kelly wrote: On

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

LGTM2! On Fri, Oct 27, 2023 at 1:50 PM Ben Kelly wrote: > > > On Fri, Oct 27, 2023 at 4:45 PM Chris Harrelson > wrote: > >> Hi, >> >> This plan makes sense to me. It's an unusual situation but IMO justified >> given the difficulty of the goal. One last piece though: per the Blink >> launch proc

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

On Fri, Oct 27, 2023 at 4:45 PM Chris Harrelson wrote: > Hi, > > This plan makes sense to me. It's an unusual situation but IMO justified > given the difficulty of the goal. One last piece though: per the Blink > launch process >

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

LGTM2 On Thu, Oct 26, 2023 at 10:30 AM Mike Taylor wrote: > Thanks for the design doc! The quote from kleber@ really helped me to > understand the use case and developer need. It sounds like this is a small > tweak to fenced frame event-level reporting, which is itself a temporary > stepping sto

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

Hi, This plan makes sense to me. It's an unusual situation but IMO justified given the difficulty of the goal. One last piece though: per the Blink launch process you need to specify an end milestone that is <= 6 release after the

Re: [blink-dev] Re: Intent to Ship: FedCM extensions: Error API and Auto-Selected Flag API

Thanks Nicolás and Yi. LGTM1 % the PRs landing before this ships, and assuming Mozilla does not have feedback that materially changes the API shape. If that's the case, can you report back? thanks, Mike On 10/26/23 10:27 AM, Nicolás Peña wrote: For the record, we did request reviews: here <

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

Per that document, Mode B Chrome instances will also be labeled. On Friday, October 27, 2023 at 2:52:33 PM UTC-5 wande...@chromium.org wrote: > FYI, the specific labels to be sent are listed here: > > https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing/#mode-a > > Specifically, t

Re: [blink-dev] Intent to Ship: WebGPU on Android

LGTM1 - this is an easy one :) On Fri, Oct 27, 2023 at 1:21 PM 'Brandon Jones' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsbajo...@chromium.org, cwal...@chromium.org > > Explainerhttps://gpuweb.github.io/gpuweb/explainer/ > > Specificationhttps://www.w3.org/TR/webgpu > > Design

[blink-dev] Intent to Ship: WebGPU on Android

Contact emailsbajo...@chromium.org, cwal...@chromium.org Explainerhttps://gpuweb.github.io/gpuweb/explainer/ Specificationhttps://www.w3.org/TR/webgpu Design docs https://gpuweb.github.io/gpuweb https://gpuweb.github.io/gpuweb/wgsl https://gpuweb.github.io/gpuweb/explainer Summary This Intent t

Re: [blink-dev] Intent to Ship: MediaCapabilities: Query HDR support with decodingInfo()

LGTM3 On Fri, Oct 27, 2023 at 1:01 PM Dale Curtis wrote: > Looks like this got approved on chrome status, but is still missing an > LGTM3. Anyone else want to weigh in? > > - dale > > On Wed, Oct 25, 2023 at 12:35 PM Mike Taylor > wrote: > >> LGTM2 >> On 10/25/23 3:06 PM, 'Rick Byers' via blink

Re: [blink-dev] Intent to Ship: MediaCapabilities: Query HDR support with decodingInfo()

Looks like this got approved on chrome status, but is still missing an LGTM3. Anyone else want to weigh in? - dale On Wed, Oct 25, 2023 at 12:35 PM Mike Taylor wrote: > LGTM2 > On 10/25/23 3:06 PM, 'Rick Byers' via blink-dev wrote: > > Looks pretty straightforward to me, especially with Safari

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

FYI, the specific labels to be sent are listed here: https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing/#mode-a Specifically, the "label_only_1", "label_only_2", "label_only_3", "label_only_4", and "label_only_5" labels. Note, the "control_1.*" labels are not being enabled yet.

[blink-dev] Re: Intent to Ship: Shared Storage API Enhancements

FYI: Update Shared Storage API HTTP request header name to 'Sec-Shared-Storage-Writable' As previously mentioned in our Intent to Ship, as part of the M119 Enhancements to the Shared Storage API , M119 will allow writing and deleting from Shared S

[blink-dev] Web-Facing Change PSA: Set IndexedDB transaction durability to `relaxed` by default

Contact emailsest...@chromium.org, a...@chromium.org Specificationhttps://www.w3.org/TR/IndexedDB Summary IndexedDB offers two durability modes for readwrite transactions: `relaxed` and `strict`. This may be specified via the optional `options` struct when creating a transaction. See https://dev

Re: [blink-dev] Intent to Experiment: Cookie Deprecation Labeling

Exposing a new header and JS API temporarily for the purposes of an experiment (outside the context of an OT) is not something we've ever done before. But given the scope and requirements of this experiment and our desire to help enable the ecosystem to reason about it, it seems absolutely like the

Re: [blink-dev] Intent to Ship: CSS masking

LGTM3 On Fri, Oct 27, 2023, 4:24 AM Mike Taylor wrote: > LGTM2. > > (I filed https://github.com/whatwg/compat/issues/252 - thanks for the > doc!) > On 10/27/23 5:55 AM, Philip Jägenstedt wrote: > > LGTM1 > > Thanks for writing that up, Philip! I believe that should be helpful for > release notes

Re: [blink-dev] Intent to Ship: CSS masking

LGTM2. (I filed https://github.com/whatwg/compat/issues/252 - thanks for the doc!) On 10/27/23 5:55 AM, Philip Jägenstedt wrote: LGTM1 Thanks for writing that up, Philip! I believe that should be helpful for release notes and MDN docs down the line. On Thu, Oct 26, 2023 at 7:20 PM 'Philip R

Re: [blink-dev] Intent to Ship: CSS masking

LGTM1 Thanks for writing that up, Philip! I believe that should be helpful for release notes and MDN docs down the line. On Thu, Oct 26, 2023 at 7:20 PM 'Philip Rogers' via blink-dev < blink-dev@chromium.org> wrote: > > > On Wednesday, October 25, 2023 at 7:24:34 AM UTC-7 Mike Taylor wrote: > >

Re: [blink-dev] Re: Intent to Ship: WebGPU maxBindGroupsPlusVertexBuffers limit

LGTM3 given some basic tests added to CTS. François discussed in chat, and some basic tests are possible to confirm existence and relationship to other attributes, tracked by https://github.com/gpuweb/cts/issues/3106. On Fri, Oct 27, 2023 at 11:13 AM François Beaufort wrote: > Here's the CTS is

Re: [blink-dev] Re: Intent to Ship: WebGPU maxBindGroupsPlusVertexBuffers limit

Here's the CTS issue for maxBindGroupsPlusVertexBuffers: https://github.com/gpuweb/cts/issues/2983 Once we'll have validation, we'll be able to add CTS tests. See https://source.chromium.org/chromium/chromium/src/+/main:third_party/dawn/src/dawn/native/Device.cpp;l=1808;drc=b6a33c6fb6097fb097b7e60a

Re: [blink-dev] Re: Intent to Ship: WebGPU maxBindGroupsPlusVertexBuffers limit

Hi François, Corentin, I greped for "maxBindGroupsPlusVertexBuffers" in a checkout of https://github.com/gpuweb/cts but couldn't find any tests. Should there be shared tests there? Best regards, Philip On Wed, Oct 25, 2023 at 4:25 PM Mike Taylor wrote: > LGTM2 > On 10/25/23 4:32 AM, 'François