Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

On Tue, Jun 11, 2024 at 7:43 PM Akash Nadan wrote: > Hi Yoav, > > The debug signals that will be reported on are documented here: > https://github.com/WICG/attribution-reporting-api/blob/main/verbose_debugging_reports.md > Thanks! Should that be part of the spec? > > These are the same debug s

Re: [blink-dev] Intent to Experiment: WebGPU Subgroups experimentation

What milestones do you want the experiment to run? On Tue, Jun 11, 2024 at 9:02 PM 'Alan Baker' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsalanba...@google.com > > Explainerhttps://github.com/gpuweb/gpuweb/blob/main/proposals/subgroups.md > > SpecificationNone > > Summary > >

Re: [blink-dev] Re: Intent to Ship: document.caretPositionFromPoint API

On Thu, Jun 6, 2024 at 9:03 PM 'Siye Liu' via blink-dev < blink-dev@chromium.org> wrote: > Reviews requested. > > Thanks, > Siye > > On Thursday, June 6, 2024 at 9:47:37 AM UTC-7 Chris Harrelson wrote: > >> Hi, please fill out these reviews on your chromestatus entry: >> >> [image: image.png] >> >

Re: [blink-dev] Intent to Ship: Protected Audience - Fix implementation and spec for renderSize

LGTM1 This sounds like a web-exposed bug fix, and I agree that the risk seems low. On Tue, Jun 11, 2024 at 6:10 PM 'Xiaochen Zhou' via blink-dev < blink-dev@chromium.org> wrote: > I have started the requests, thank you. This item was originated from a > previous launch: > https://chromestatus.co

Re: [blink-dev] Intent to Ship: Snap Events

LGTM1 This seems like a useful addition, with lots of developer demand. While more detailed explainers would have been helpful, I don't feel it's a blocker atm, as the demos provided helped me understand what we're shipping and how developers will use it. On Tue, Jun 11, 2024 at 4:46 PM Adam Argy

Re: [blink-dev] Re: Intent to Ship: No-Vary-Search support for prerender

Now, when it looks like this will be shipped, can you please update the stalled standard-position issues for Mozilla and WebKit so that they know that we'll proceed with it. /Daniel On 2024-06-06 19:21, Vladimir Levin wrote: LGTM3 On Thu, Jun 6, 2024 at 12:45 PM Chris Harrelson wrote:

Re: [blink-dev] Intent to Ship: Protected Audience - Fix implementation and spec for renderSize

LGTM2 /Daniel On 2024-06-12 13:09, Yoav Weiss (@Shopify) wrote: LGTM1 This sounds like a web-exposed bug fix, and I agree that the risk seems low. On Tue, Jun 11, 2024 at 6:10 PM 'Xiaochen Zhou' via blink-dev wrote: I have started the requests, thank you. This item was originated

Re: [blink-dev] Intent to Experiment: WebGPU Subgroups experimentation

LGTM to experiment M128-131 inclusive On Wed, Jun 12, 2024 at 4:11 PM Alan Baker wrote: > I've updated the feature. We'd like to start in milestone 128 for 4 > milestones. > > On Wed, Jun 12, 2024 at 6:06 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> What milestones do you wan

Re: [blink-dev] Intent to Experiment: WebGPU Subgroups experimentation

Please kick-off the chrome status reviews on Privacy, Security and Debuggability before turning on the experiment. On Wed, Jun 12, 2024 at 4:13 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM to experiment M128-131 inclusive > > On Wed, Jun 12, 2024 at 4:11 PM Alan Baker wrote:

Re: [blink-dev] Intent to Ship: Snap Events

LGTM2 /Daniel On 2024-06-12 13:14, Yoav Weiss (@Shopify) wrote: LGTM1 This seems like a useful addition, with lots of developer demand. While more detailed explainers would have been helpful, I don't feel it's a blocker atm, as the demos provided helped me understand what we're shipping and

Re: [blink-dev] Intent to Experiment: WebGPU Subgroups experimentation

I've updated the feature. We'd like to start in milestone 128 for 4 milestones. On Wed, Jun 12, 2024 at 6:06 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > What milestones do you want the experiment to run? > > On Tue, Jun 11, 2024 at 9:02 PM 'Alan Baker' via blink-dev < > blink-dev@

Re: [blink-dev] Re: Intent to Ship: No-Vary-Search support for prerender

> Now, when it looks like this will be shipped, can you please update the stalled standard-position issues for Mozilla and WebKit so that they know that we'll proceed with it. The standard position issues for both Mozilla and WebKit were updated. On Wednesday, June 12, 2024 at 7:42:05 AM UTC-4 D

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

Hi Yoav, The list of debugging signals is part of the spec: https://wicg.github.io/attribution-reporting-api/#source-debug-data-type https://wicg.github.io/attribution-reporting-api/#trigger-debug-data-type Thanks, Nan On Wednesday, June 12, 2024 at 4:27:41 AM UTC-4 Yoav Weiss wrote: > On Tue,

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

LGTM1 On Wed, Jun 12, 2024 at 5:21 PM Nan Lin wrote: > Hi Yoav, > > The list of debugging signals is part of the spec: > > https://wicg.github.io/attribution-reporting-api/#source-debug-data-type > https://wicg.github.io/attribution-reporting-api/#trigger-debug-data-type > Awesome, thanks! >

Re: [blink-dev] Intent to Ship: Snap Events

LGTM3 Please do ping this thread with an updated explainer once you have it. On Wed, Jun 12, 2024 at 4:16 PM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2024-06-12 13:14, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > This seems like a useful addition, with lots of developer demand. While > more

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

LGTM2 On 6/12/24 11:25 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Wed, Jun 12, 2024 at 5:21 PM Nan Lin wrote: Hi Yoav, The list of debugging signals is part of the spec: https://wicg.github.io/attribution-reporting-api/#source-debug-data-type https://wicg.github.io/attributio

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

LGTM3 On Wed, Jun 12, 2024 at 5:42 PM Mike Taylor wrote: > LGTM2 > On 6/12/24 11:25 AM, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > On Wed, Jun 12, 2024 at 5:21 PM Nan Lin wrote: > >> Hi Yoav, >> >> The list of debugging signals is part of the spec: >> >> https://wicg.github.io/attribution-repor

Re: [blink-dev] Intent to Ship: WebAuthn hints

On Mon, Jun 3, 2024 at 10:59 PM Adam Langley wrote: > Contact emails...@chromium.org > > Specificationhttps://w3c.github.io/webauthn/#enum-hints > > Summary > > The new `hints` parameter[1] in WebAuthn requests allows sites to provide > guidance to browsers to guide their UI. The canonical use ca

Re: [blink-dev] Intent to Ship: WebAuthn hints

Hi, Is it possible to put together a small explainer for this. It's a bit difficult to understand what this hint would control. Do you have examples? Thanks, Vlad On Wednesday, June 5, 2024 at 1:11:27 PM UTC-4 Adam Langley wrote: > On Tue, Jun 4, 2024 at 7:26 PM Mike Taylor wrote: > >> Review

Re: [blink-dev] Intent to Ship: Protected Audience - Fix implementation and spec for renderSize

LGTM3 On Wed, Jun 12, 2024 at 4:06 PM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2024-06-12 13:09, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > This sounds like a web-exposed bug fix, and I agree that the risk seems > low. > > On Tue, Jun 11, 2024 at 6:10 PM 'Xiaochen Zhou' via blink-dev < > b

Re: [blink-dev] Intent to Ship: Support 'color-interpolation: linearrgb' on SVG gradients

LGTM1 On Tue, Jun 11, 2024 at 10:23 AM Fredrik Söderquist wrote: > On Tue, Jun 11, 2024 at 6:08 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Mon, Jun 10, 2024 at 11:25 AM Fredrik Söderquist wrote: >> >>> Contact email...@opera.com >>> >>> ExplainerNone >>> >>> Speci

Re: [blink-dev] Intent to Ship: Support 'color-interpolation: linearrgb' on SVG gradients

LGTM2 On Wed, Jun 12, 2024 at 5:50 PM Chris Harrelson wrote: > LGTM1 > > On Tue, Jun 11, 2024 at 10:23 AM Fredrik Söderquist wrote: > >> On Tue, Jun 11, 2024 at 6:08 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> >>> >>> On Mon, Jun 10, 2024 at 11:25 AM Fredrik Söderquist

Re: [blink-dev] Intent to Ship: Support 'color-interpolation: linearrgb' on SVG gradients

LGTM3 /Daniel On 2024-06-12 17:50, Yoav Weiss (@Shopify) wrote: LGTM2 On Wed, Jun 12, 2024 at 5:50 PM Chris Harrelson wrote: LGTM1 On Tue, Jun 11, 2024 at 10:23 AM Fredrik Söderquist wrote: On Tue, Jun 11, 2024 at 6:08 AM Yoav Weiss (@Shopify) wrote:

[blink-dev] Intent to Implement and Ship: aria-rowindextext and aria-colindextext

Contact emails dan...@microsoft.com Explainer No formal explainer but https://github.com/w3c/aria/issues/667 discusses use cases and alternatives. Specification https://w3c.github.io/aria/#aria-colindextext, https://w3c.github.io/aria/#aria-rowindextext Su

[blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

Contact emails sni...@microsoft.com sa...@microsoft.com Specification https://w3c.github.io/clipboard-apis/#optional-data-types-x Design docs None. See summary. Summary On Windows, popular native apps [1] use UTF-8 format to read/write SVG

Re: [blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

Could you add this detail to the Clipboard spec, since it seems to be needed for programs to be interoperable? Thanks, Jeffrey On Wed, Jun 12, 2024 at 11:43 AM 'Anupam Snigdha' via blink-dev < blink-dev@chromium.org> wrote: > *Contact emails* > *sni...@microsoft.com * > *sa...@microsoft.com * >

Re: [blink-dev] Re: Intent to Ship: document.caretPositionFromPoint API

Yes, these tests will all pass if we enable the runtime flag `CaretPositionFromPoint`. The few Mozilla failures do represent their non-spec compliant behavior. Thanks, Siye On Wednesday, June 12, 2024 at 4:03:35 AM UTC-7 yoav...@chromium.org wrote: > On Thu, Jun 6, 2024 at 9:03 PM 'Siye Liu'

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

Daniel, My initial metrics were significantly higher due to the presence of a cookie named “receive-cookie-deprication”. This is a cookie , Google is using to

Re: [EXTERNAL] Re: [blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

It's already in the spec: https://w3c.github.io/clipboard-apis/#:~:text=Let%20payload%20be%20the%20result%20of%20UTF%2D8%20decoding%20item%E2%80%99s%20underlying%20byte%20sequence.

Re: [EXTERNAL] Re: [blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

The text in https://w3c.github.io/clipboard-apis/#to-write-blobs-to-clipboard says to decode from UTF-8 bytes into scalar values, and then to write those scalar values into the clipboard. My impression of the change you're announcing in this thread is that the system clipboard actually contains byt