Re: [blink-dev] Intent to Ship: Rename position-try-options to position-try-fallbacks

On Wed, Jul 17, 2024 at 10:29 PM Vladimir Levin wrote: > > > On Wed, Jul 10, 2024 at 6:34 PM Mason Freed wrote: > >> {NOTE: this is a replacement of this chromestatus >> , which has the wrong >> feature type and cannot be changed.} >> Contact em

Re: [blink-dev] Intent to Ship: WebGPU extended range (HDR) support

On Wednesday, July 17, 2024 at 10:41:26 AM UTC+9 Domenic Denicola wrote: This looks like a nice straightforward feature. Just one potential spec issue... On Tue, Jul 16, 2024 at 11:19 PM 'Christopher Cameron' via blink-dev < blink-dev@chromium.org> wrote: Hello blink-dev! This is the first fe

Re: [blink-dev] Fwd: Intent to Extend Experiment: Protected Audience Bidding & Auction Services

The draft PR describes the basic API. There are some options we've recently added to navigator.getInterestGroupAdAuctionData()` to provide more control over what gets put in the encrypted request (see the explainer pull request here: https://github.com/WICG/turtledove/pull/1183) which are not ye

Re: [blink-dev] Turning off use_v8_context_snapshot in non-production builds by default

On Wed, Jul 17, 2024 at 4:18 PM Erik Staab wrote: > Let me try to summarize this thread and clarify a few points to help guide > us to a decision. > > 1) The snapshot provides a significant performance improvement and there > are currently no alternate strategies that would be better for build ti

Re: [blink-dev] Intent to Ship: Private Aggregation API: filtering IDs

On Mon, Jul 15, 2024 at 11:03 AM Mike Taylor wrote: > On 7/12/24 10:44 AM, Alex Turner wrote: > > On Wed, Jul 10, 2024 at 11:25 AM Mike Taylor > wrote: > >> On 7/8/24 4:05 PM, Alex Turner wrote: >> >> >> Interoperability and Compatibility >> >> The Aggregation Service (used to process the aggreg

Re: [blink-dev] Intent to Ship: Rename position-try-options to position-try-fallbacks

On Wed, Jul 10, 2024 at 6:34 PM Mason Freed wrote: > {NOTE: this is a replacement of this chromestatus > , which has the wrong > feature type and cannot be changed.} > Contact emailsmas...@chromium.org, andr...@chromium.org > > ExplainerNone > >

Re: [blink-dev] Turning off use_v8_context_snapshot in non-production builds by default

Let me try to summarize this thread and clarify a few points to help guide us to a decision. 1) The snapshot provides a significant performance improvement and there are currently no alternate strategies that would be better for build times 2) We need test coverage for the snapshot code path since

[blink-dev] Intent to Prototype: Shared Storage API enhancement (allow cross-origin script in addModule & align createWorklet)

Contact emails cam...@chromium.org, jkar...@chromium.org, yao...@chromium.org, ashame...@google.com Explainer https://github.com/WICG/shared-storage/blob/main/README.md Specification https://github.com/WICG/shared-storage/pull/161 Summary and Motivation We have received feedback from develop

Re: [blink-dev] Re: Intent to Experiment: Element Capture

I registered a token for the origin trial but it doesn't seem to work. Is it not active yet? Demo: https://whatpwacando.today/element-capture Op dinsdag 21 mei 2024 om 12:05:58 UTC+2 schreef Elad Alon: > Thank you for the LGTMs. > > A quick update that we have discussed the matter with the OT C

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

Hey Vlad, I agree that deleting the affected cookies seems to be the least risky > behavior here. Is this plan to roll out via Finch and monitor for bad > breakages? > Unfortunately it is not possible to roll out network feature changes via Finch to WebView, since WebView may sometimes use the coo

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

LGTM3 to extend experimentation up to and including M131, but no further. Like Vlad, I'd like to see clear evidence of significant progress before considering further extensions. I'm very unhappy with the way this OT was managed. I'm LGTMing as I don't want your partners to bear the costs, but I w

Re: [blink-dev] Intent to Experiment: FedCM Bundle 6: Continuation API, Scope API, Scaling Well-Known, Custom account labels

Sorry, one more request, can we shift this OT to 127 until 130? It took a while for our partner to get ready for the trial. Christian On Tue, Jul 16, 2024 at 12:43 PM Chris Harrelson wrote: > > > On Tue, Jul 16, 2024 at 9:34 AM Christian Biesinger < > cbiesin...@chromium.org> wrote: > >> Hi, >>

Re: [blink-dev] Intent to Ship: Web Authentication API: JSON serialization methods

Work is underway to enable WebAuthn broadly on WebView. As far as I'm aware, that work hasn't quite roll out yet due to some dependency on the Android side. I'll ask the people working on that to ensure they update the MDN compat table once we know a minimum version. Once WebAuthn is available in

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

On Wed, Jul 17, 2024 at 1:28 PM 'Simon Hangl' via blink-dev < blink-dev@chromium.org> wrote: > Thank you for the quick response. Just one correction: the agreement > contained an extension until (including) M136 (see my reponse above). > For now, my LGTM only applies up to and including M131. If

Re: [blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

On 7/17/24 10:18 AM, Mustaq Ahmed wrote: > Can you ask for WebKit's position? Or maye there's at least a pointer to working group discussions they participated in? - Safari doesn't yet support PointerEvent.getCoalescedEvents(), so we can't ask for their position on secure/non-secure context d

Re: [blink-dev] Intent to Deprecate and Relaunch: CHIPS on WebView

Thank you for all of the context. I agree that deleting the affected cookies seems to be the least risky behavior here. Is this plan to roll out via Finch and monitor for bad breakages? Also, could you start the various reviews on the chromestatus entry? [image: chipsna.png] Thanks, Vlad On Thu

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

Thank you for the quick response. Just one correction: the agreement contained an extension until (including) M136 (see my reponse above). On Wednesday, July 17, 2024 at 6:45:44 PM UTC+2 Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2024-07-17 18:40, Vladimir Levin wrote: > > As you mentioned,

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

LGTM2 /Daniel On 2024-07-17 18:40, Vladimir Levin wrote: As you mentioned, this is not the intended use of OTs. However, since the feature needs IWAs to ship, and IWAs are well on track towards shipping, I'm inclined to allow this extension. That being said, I am hopeful that this will be the

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

As you mentioned, this is not the intended use of OTs. However, since the feature needs IWAs to ship, and IWAs are well on track towards shipping, I'm inclined to allow this extension. That being said, I am hopeful that this will be the last extension to the feature. Due to the nature of this situ

Re: [blink-dev] Re: Intent to Ship: Attribution Reporting Feature: Flexible contributions filtering

LGTM1 On Fri, Jul 12, 2024 at 1:10 PM 'Akash Nadan' via blink-dev < blink-dev@chromium.org> wrote: > Hi All, > > > Just adding some additional detail regarding the interoperability and > compatibility of this feature: > > > Interoperability and Compatibility > > This change is optional and will b

Re: [blink-dev] Re: Intent to Ship: AudioContext.onerror

LGTM3 /Daniel On 2024-07-16 17:23, Mike Taylor wrote: LGTM2 On 7/15/24 10:55 PM, Domenic Denicola wrote: LGTM1, thanks for the prompt action! On Mon, Jul 15, 2024 at 11:22 PM Hongchan Choi wrote: Hi Domenic, Thanks for your input! I've addressed the issue you opened with 2

[blink-dev] Web-Facing Change PSA: Coalesced/predicted events in untrusted PointerEvents will retain original targets

Contact emailsmus...@chromium.org Specification https://w3c.github.io/pointerevents/#populating-and-maintaining-the-coalesced-and-predicted-events-lists Summary For untrusted (i.e. JS constructed) PointerEvents, the events returned by PointerEvent.getCoalescedEvents() and PointerEvent.getPredict

Re: [blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

> Can you ask for WebKit's position? Or maye there's at least a pointer to working group discussions they participated in? - Safari doesn't yet support PointerEvent.getCoalescedEvents(), so we can't ask for their position on secure/non-secure context differences: https://developer.mozilla.org/en-U

[blink-dev] Intent to Prototype: Add bugfix version number to User-Agent string on Bling

Contact emails janice...@chromium.org, miketa...@chromium.org Explainer None. This is a minor change and we are sharing it to provide transparency into changes that we are implementing. Specification https://www.rfc-editor.org/rfc/rfc9110#field.user-agent Summary User Agent (UA) strings in

Re: [blink-dev] Intent to Ship: Web Authentication API: JSON serialization methods

On Sat, Jul 13, 2024 at 1:42 AM 'Martin Kreichgauer' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsmarti...@google.com > > Explainer > https://github.com/w3c/webauthn/wiki/Explainer:-JSON-Serialization-Methods > > Specificationhttps://w3c.github.io/webauthn/#publickeycredential >