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

LGTM2 % administrative shenanigans regarding the review gates On Thu, Oct 26, 2023 at 2:16 AM Mike Taylor wrote: > Sorry, we're still learning this new chromestatus process (and a similar > concern came up in our API OWNERs meeting earlier today). My understanding > is that we should have _somet

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

LGTM3 On Wed, Oct 25, 2023 at 8:44 PM Mike Taylor wrote: > LGTM2 > On 10/25/23 2:39 PM, 'Rick Byers' via blink-dev wrote: > > FWIW since the PR has landed, the correct link to reference the spec is > https://fedidcg.github.io/FedCM/#browser-api-login-status. Since WebKit > has expressed some int

Re: [blink-dev] Intent to Ship: Permissions policy violation reports

LGTM3 On Wed, Oct 25, 2023 at 9:36 PM Mike Taylor wrote: > LGTM2 > On 10/25/23 3:00 PM, 'Rick Byers' via blink-dev wrote: > > Looks like a pretty straightforward combination of these established > patterns, I like it! LGTM1 > > On Wed, Oct 25, 2023 at 8:42 AM Ian Clelland > wrote: > >> >> >> On

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

Sorry, we're still learning this new chromestatus process (and a similar concern came up in our API OWNERs meeting earlier today). My understanding is that we should have _something_ in there, so perhaps the right thing to do is to request the reviews stating that these are normally N/A for TC3

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

Those gates are not applicable for most TC39 stage 3 features, including this one. Are you asking them to be marked as such or that we requested reviews for it? On Wed, Oct 25, 2023 at 4:00 PM Mike Taylor wrote: > Oops... sent too early. Can you also please request reviews for the rest > of the

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

Hi Paul, On 10/19/23 7:01 PM, Paul Jensen wrote: Contact emails pauljen...@chromium.org Explainer clearOriginJoinedAdInterestGroups(): https://github.com/WICG/turtledove/pull/829 interest group limit changes: https://github

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

Hi Liam! On 10/20/23 4:37 PM, 'Liam Brady' via blink-dev wrote: Contact emails shivani...@chromium.org jkar...@chromium.org lbr...@google.com Explainer(s) Send Automatic Beacons To All Registered Desti

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

We sync’d with @bvandersloot-mozilla in FedIdCG [1] and they have confirmed that it’s on their list. [1] https://github.com/fedidcg/meetings/blob/main/2023/2023-10-02-notes.md#notes On Wed, Oct 25, 2023 at 6:51 PM Mike Taylor wrote: > On 10/25/23 4:14 P

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

Oops... sent too early. Can you also please request reviews for the rest of the review gates in the chromestatus entry? On 10/25/23 6:57 PM, Mike Taylor wrote: LGTM1. It's encouraging that Firefox Nightly ship

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

LGTM1. It's encouraging that Firefox Nightly shipped this a few months back with no reported regressions thus far. On 10/25/23 6:39 PM, Rezvan Mahdavi Hezaveh wrote: Contact emails s...@chromium.org, rez...@chromium.org

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

On 10/25/23 4:14 PM, Yi Gu wrote: Thanks Yoav for the review! > It'd be useful to write a short (inline?) explainer here outlining what this does and how it'd look like. Specifically, would we start throwing on errors in scenarios that silently failed before? For the Error API, it allows Id

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

Contact emails...@chromium.org, rez...@chromium.org Explainerhttps://github.com/tc39/proposal-array-from-async Specificationhttps://tc39.es/proposal-array-from-async Summary Array.fromAsync is the async version of Array.from. It takes async iterables, iterates them, and collects the results int

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

*Contact emails* johni...@chromium.org, wanderv...@chromium.org, lin...@chromium.org *Explainer* https://github.com/privacysandbox/tpcd-labeling/blob/main/cookie_deprecation_labeling_explainer.md https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing *Specification* None *Summary* T

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

I found a similar API canPlayType for media element that informs the user about the supported MIME types. So, it looks like there is some precedent for this kind of API on the web. -Anupam __

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

Thanks Yoav for the review! > It'd be useful to write a short (inline?) explainer here outlining what this does and how it'd look like. Specifically, would we start throwing on errors in scenarios that silently failed before? For the Error API, it allows IdP to signal to the browser about the sig

Re: [blink-dev] Re: [EXTERNAL] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML

Hi Anupam, I've spent an hour or so trying to follow the history of this discussion, there's obviously been a lot of debate in this space over the years. I think your answer to Thomas's question is what really clarified this specific proposal to me - you're specifically interested in the case where

Re: [blink-dev] Third-party deprecation trial

Thanks for your explanation! On Wed, Oct 25, 2023 at 12:20 PM Ben Kelly wrote: > > > On Wed, Oct 25, 2023 at 3:12 PM J C wrote: > >> Thanks, Let me clarify a bit on my example. >> >> "A" is the writer of the cookie under the server sent cookie with the >> top-level context. "B" is reading the c

Re: [blink-dev] Intent to Ship: Permissions policy violation reports

LGTM2 On 10/25/23 3:00 PM, 'Rick Byers' via blink-dev wrote: Looks like a pretty straightforward combination of these established patterns, I like it! LGTM1 On Wed, Oct 25, 2023 at 8:42 AM Ian Clelland wrote: On Wed, Oct 25, 2023 at 4:35 AM Yoav Weiss wrote: On Tue, O

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

LGTM2 On 10/25/23 3:06 PM, 'Rick Byers' via blink-dev wrote: Looks pretty straightforward to me, especially with Safari already shipping. LGTM1 On Wed, Oct 18, 2023 at 7:18 PM Dale Curtis wrote: Contact emails v...@microsoft.com, gw...@microsoft.com,

Re: [blink-dev] Third-party deprecation trial

On Wed, Oct 25, 2023 at 3:12 PM J C wrote: > Thanks, Let me clarify a bit on my example. > > "A" is the writer of the cookie under the server sent cookie with the > top-level context. "B" is reading the cookie under the embedded iframe > hosted by Site "C"("123.com"). Both A and B are from the sa

Re: [blink-dev] Re: Intent to Ship: CSS Scrollbars: scrollbar-color, scrollbar-width

I've updated chromestatus to reflect this aswell. On Wednesday, 25 October 2023 at 20:18:07 UTC+1 blink-dev wrote: > We're going to skip Android WebView for now so that this can ship in > Chrome without delays, but separately we're going to try updating the > WebView behavior here to be less we

Re: [blink-dev] Re: Intent to Ship: CSS Scrollbars: scrollbar-color, scrollbar-width

We're going to skip Android WebView for now so that this can ship in Chrome without delays, but separately we're going to try updating the WebView behavior here to be less weird, and if that works out without app compat problems we should be able to enable these CSS features in WebView too (just po

Re: [blink-dev] Third-party deprecation trial

Thanks, Let me clarify a bit on my example. "A" is the writer of the cookie under the server sent cookie with the top-level context. "B" is reading the cookie under the embedded iframe hosted by Site "C"("123.com"). Both A and B are from the same domain of " my.connect.aws.com", where A is a top-l

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

Looks pretty straightforward to me, especially with Safari already shipping. LGTM1 On Wed, Oct 18, 2023 at 7:18 PM Dale Curtis wrote: > Contact emailsv...@microsoft.com, gw...@microsoft.com, > gur...@microsoft.com, dalecur...@chromium.org > > Explainer > https://github.com/w3c/media-capabilities

Re: [blink-dev] Intent to Ship: Permissions policy violation reports

Looks like a pretty straightforward combination of these established patterns, I like it! LGTM1 On Wed, Oct 25, 2023 at 8:42 AM Ian Clelland wrote: > > > On Wed, Oct 25, 2023 at 4:35 AM Yoav Weiss wrote: > >> >> >> On Tue, Oct 24, 2023 at 7:24 PM Ian Clelland >> wrote: >> >>> Contact emailsicl

Re: [blink-dev] Third-party deprecation trial

On Wed, Oct 25, 2023 at 2:49 PM J C wrote: > Great! Thanks for clarifying. > > Just quick follow up, for the new trial, say if "A" writes and reads a > third party cookie on "B", my understanding is "A" should request for the > third-party cookie Deprecation trial? > It will be a third-party dep

Re: [blink-dev] Third-party deprecation trial

Great! Thanks for clarifying. Just quick follow up, for the new trial, say if "A" writes and reads a third party cookie on "B", my understanding is "A" should request for the third-party cookie Deprecation trial? Mike Taylor 于2023年10月25日周三 11:44写道： > Hi there, > On 10/25/23 2:09 PM, J C wrote:

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

LGTM2 On 10/25/23 2:39 PM, 'Rick Byers' via blink-dev wrote: FWIW since the PR has landed, the correct link to reference the spec is https://fedidcg.github.io/FedCM/#browser-api-login-status. Since WebKit has expressed some interest in using this API in other scenarios than just FedCM I imagin

Re: [blink-dev] Third-party deprecation trial

Hi there, On 10/25/23 2:09 PM, J C wrote: I am looking forward to requesting this third-party deprecation trial . I am

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

FWIW since the PR has landed, the correct link to reference the spec is https://fedidcg.github.io/FedCM/#browser-api-login-status. Since WebKit has expressed some interest in using this API in other scenarios than just FedCM I imagine there may be a request at some point to move it out of the FedCM

[blink-dev] Third-party deprecation trial

Hi All, I am looking forward to requesting this third-party deprecation trial . I am a little bit confused whether "Re

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

Just requested the reviews. On Wed, Oct 25, 2023 at 11:21 AM Yoav Weiss wrote: > Can you kick off the review on the 5 other review categories in the > chromestatus entry? > > On Friday, October 20, 2023 at 10:37:37 PM UTC+2 blink-dev wrote: > >> Contact emails >> >> shivani...@chromium.org jkar.

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

On Wed, Oct 25, 2023 at 8:30 AM Yoav Weiss wrote: > > > On Thursday, October 19, 2023 at 1:18:44 AM UTC+2 blink-dev wrote: > > Contact emailsv...@microsoft.com, gw...@microsoft.com, gurvir@ > microsoft.com, dalecur...@chromium.org > > Explainerhttps://github.com/w3c/media-capabilities/blob/main/

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

On 10/20/23 2:27 PM, 'Philipp Hancke' via blink-dev wrote: Contact emails * phan...@microsoft.com, bernard.ab...@microsoft.com * Explainer * None * For those looking for an explainer, hope down to the design docs sectio

Re: [blink-dev] Re: Intent to Extend Experiment: No-Vary-Search header, Speculation Rules expects_no_vary_search support in prefetch cache

Apologies - this intent didn't show up in our review tooling (cc Jason), so it's slipped under the radar. I believe y'all have met the bar to extend again, given that the below criteria are largely done: Draft spec TAG review bit.ly/blink-signals requests Outreach for feedback from the spec c

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

Understood. 1. *Is there any action required from us until general rollout (when `unload` isn’t fired anymore)?* 2. *Is there a list of this restricted set domains with which you’re experimenting?* Want to know if ours are included 3. *We should have `pagehide` replacement by

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

To add to what Christian mentioned, we do have WPT tests for this feature here and they have been running in Chromium CQ, so it is only WPT.fyi that is

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

It seems I may have a reviewer *now*, maybe. It's been very hard to get someone to review this and I don't know if I will be able to get a timely lgtm, so I am hoping that this I2S won't get blocked on this, since this is mostly outside my control. (I don't think past I2S were blocked on wpt tests

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

LGTM3 On 10/25/23 11:25 AM, Chris Harrelson wrote: LGTM2 On Wed, Oct 25, 2023 at 8:23 AM Yoav Weiss wrote: LGTM1 On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes wrote: There has not been an update on this ITS in 8 days. What's the expected timel

[blink-dev] PSA: Storage Access API & dedicated workers

Hello all, Just wanted to give an FYI that I will be submitting a change that makes dedicated workers "inherit" the storage-access status of their parent (whether the parent is a document, or is another worker). This behavior is not specified by the Storage Access

Re: [blink-dev] Intent to ship: The Login Status API and its use in FedCM

Hi Christian, Do you have a reviewer for https://github.com/web-platform-tests/wpt/pull/40709 so you can get it merged? Just like spec changes, tests are ideally merged and showing results on wpt.fyi before we ship, so that any issues are apparent and can be addressed. Best regards, Philip On We

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

On Thursday, October 19, 2023 at 1:18:44 AM UTC+2 blink-dev wrote: Contact emailsv...@microsoft.com, gw...@microsoft.com, gur...@microsoft.com , dalecur...@chromium.org Explainerhttps://github.com/w3c/media-capabilities/blob/main/ explainer.md#decode-capabilities Specificationhttps://www.w3.or

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

LGTM2 On Wed, Oct 25, 2023 at 8:23 AM Yoav Weiss wrote: > LGTM1 > > On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes wrote: > >> There has not been an update on this ITS in 8 days. What's the expected >> timeline to get the LGTMs? >> > Last week was BlinkOn and we do most review

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

LGTM1 On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes wrote: > There has not been an update on this ITS in 8 days. What's the expected > timeline to get the LGTMs? > > As the M120 branch cut is around the corner, I'll go ahead and prepare the > launch, given that this is a fea

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

Can you kick off the review on the 5 other review categories in the chromestatus entry? On Friday, October 20, 2023 at 10:37:37 PM UTC+2 blink-dev wrote: > Contact emails > > shivani...@chromium.org jkar...@chromium.org lbr...@google.com > Explainer(s) > > Send Automatic Beacons To All Register

Re: [blink-dev] Re: Intent to Ship: Deprecate and remove Theora support.

On Wed, Oct 25, 2023 at 2:32 AM Philip Jägenstedt wrote: > LGTM3 with sentimental feelings. > > Back in 2010 (https://dev.opera.com/blog/re-introducing-video/) I was > cheering for Theora and shipped support in Presto. We now have other open > and RF video codecs which have been deployed on a muc

[blink-dev] Re: Intent to Extend Experiment: No-Vary-Search header, Speculation Rules expects_no_vary_search support in prefetch cache

Following up on this intent. Is there anything else needed from a process perspective to extend the experiment ? On Monday, October 2, 2023 at 6:31:39 PM UTC-4 blink-dev wrote: > Contact emails > > dome...@chromium.org, jbro...@chromium.org, liviuti...@chromium.org > > > Original I2E > > > https

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

On Monday, October 23, 2023 at 3:03:59 PM UTC+2 blink-dev wrote: Contact emails y...@chromium.org Explainer https://github.com/fedidcg/FedCM/issues/488 It'd be useful to write a short (inline?) explainer here outlining what this does and how it'd look like. Specifically, would we start thr

[blink-dev] PSA: requestAnimationFrame & DocumentTImeline timestamps time are now coarsensed

As of Chrome M120, the timestamps passed to the requestAnimationFrame() callback and the timestamp returned by document.timeline.currentTime would be coarsened according to the rules specified in https://w3c.github.io/hr-time/#dfn-coarsen-time/. This means that in cross-origin isolated contexts, th

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

LGTM2 On 10/25/23 4:32 AM, 'François Beaufort' via blink-dev wrote: On Wed, Oct 25, 2023 at 10:28 AM Yoav Weiss wrote: LGTM1 On Tuesday, October 24, 2023 at 3:32:23 PM UTC+2 blink-dev wrote: Contact emails fbeauf...@google.com, cwal...@google.com Specif

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

On 10/25/23 10:00 AM, Philip Rogers wrote: Contact emails p...@chromium.org, tcap...@chromium.org, yo...@chromium.org, f...@opera.com Explainer None Specification https://drafts.fxtf.org/css-masking/#positioned-masks Design docs https://developer.mozill

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

There has not been an update on this ITS in 8 days. What's the expected timeline to get the LGTMs? As the M120 branch cut is around the corner, I'll go ahead and prepare the launch, given that this is a feature voted to phase 4 in the W3C WebAssembly Community Group and all other approvals are the

[blink-dev] Intent to Ship: CSS masking

Contact emails...@chromium.org, tcap...@chromium.org, yo...@chromium.org, f...@opera.com ExplainerNone Specificationhttps://drafts.fxtf.org/css-masking/#positioned-masks Design docshttps://developer.mozilla.org/en-US/docs/Web/CSS/mask Summary CSS mask, and related properties such as mask-image

Re: [blink-dev] Intent to Deprecate: X-Requested-With in WebView

Hello, Do you realize that the removal of X-Requested-With header from WebView requests (without any opt-ins) is hurting website owners, since it deprives them of filtering out the traffic originating from unauthorized apps (or apps in general)? Combined with the built-in ability to tamper User

Re: [blink-dev] Intent to Ship: Permissions policy violation reports

On Wed, Oct 25, 2023 at 4:35 AM Yoav Weiss wrote: > > > On Tue, Oct 24, 2023 at 7:24 PM Ian Clelland > wrote: > >> Contact emailsiclell...@chromium.org >> >> Explainer >> https://github.com/w3c/webappsec-permissions-policy/blob/main/reporting.md >> >> Specification >> https://w3c.github.io/webap

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Wed, 25 Oct 2023 at 05:28, Kevin D. wrote: > Thanks F > > I see origin trial [1] starts soon with 119 and I need clarification: > That origin trial is a little confusing. It ended up not being implemented in 119 and may not even make it into 120. However we not roll this out generally for any

Re: [blink-dev] Re: Intent to Ship: Deprecate and remove Theora support.

LGTM3 with sentimental feelings. Back in 2010 (https://dev.opera.com/blog/re-introducing-video/) I was cheering for Theora and shipped support in Presto. We now have other open and RF video codecs which have been deployed on a much larger scale, and I'd like to think that Theora and the Xiph folks

Re: [blink-dev] Re: Intent to Ship: Deprecate and remove Theora support.

LGTM2 On Tue, Oct 24, 2023 at 7:05 PM Dale Curtis wrote: > WMF has long switched away from Theora (to VP9) per prior discussions with > them and seconded by this comment: > https://phabricator.wikimedia.org/T329258#9275042 > > Switching to H264+MP4 is not necessary to avoid this deprecation. VP9

Re: [blink-dev] Intent to Ship: Permissions policy violation reports

On Tue, Oct 24, 2023 at 7:24 PM Ian Clelland wrote: > Contact emailsiclell...@chromium.org > > Explainer > https://github.com/w3c/webappsec-permissions-policy/blob/main/reporting.md > > Specificationhttps://w3c.github.io/webappsec-permissions-policy/#reporting > > Design docs > https://github.com

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

On Wed, Oct 25, 2023 at 10:28 AM Yoav Weiss wrote: > LGTM1 > > On Tuesday, October 24, 2023 at 3:32:23 PM UTC+2 blink-dev wrote: > > Contact emails > > fbeauf...@google.com, cwal...@google.com > > Specification > > https://gpuweb.github.io/gpuweb/#dom-gpusupportedlimits- > maxbindgroupsplusvertex

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

LGTM1 On Tuesday, October 24, 2023 at 3:32:23 PM UTC+2 blink-dev wrote: Contact emails fbeauf...@google.com, cwal...@google.com Specification https://gpuweb.github.io/gpuweb/#dom-gpusupportedlimits- maxbindgroupsplusvertexbuffers Summary The WebGPU maxBindGroupsPlusVertexBuffers limit is the