Re: [blink-dev] Intent to Ship: removing the five-minute rule for

Hi all, It appears we never actually proceeded to create the ToT CL to enable this. It turns out this is implemented in a way that impacts both and speculation rules prefetch, and the latter is causing bugs for a large speculation rules prefetch deployment. See this bug

Re: [blink-dev] Intent to Ship: Explicit resource management (async)

I'm excited to see this! Is there any documented guidance for other web specs that want to integrate with this? If your spec already defines a release() or destroy() etc it can grow [Symbol.dispose]() (etc) as an alias. But do we want to encourage specs to settle on dispose() as the non-symbol nam

[blink-dev] Intent to ship: Send "Referer" header in reportEvent/automatic beacons

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Specification https://github.com/WICG/fenced-frame/pull/164 Summary Reporting beacons (e.g. reportEvent to preregistered destination URLs

Re: [blink-dev] Intent to Ship: Explicit resource management (sync)

FWIW, it looks like this is also covered by the same explainer as the as the async version (I2S

Re: [blink-dev] Intent to Ship: Explicit resource management (async)

LGTM3 Love seeing more of the best parts of C# make it into ECMAScript :-) Rick On Wed, Nov 27, 2024 at 10:56 AM Chris Harrelson wrote: > LGTM2 > > On Thu, Nov 21, 2024 at 4:12 PM Mike Taylor > wrote: > >> LGTM1 >> On 11/21/24 6:44 PM, Rezvan Mahdavi Hezaveh wrote: >> >> Contact emails rez...

Re: [blink-dev] Re: Concerns over removal of SwiftShader fallback

Hey Ashley, I suspect the M133 in the chrome status page will be updated to a later release. I also put the bug link (https://issues.chromium.org/40277080) on that page. Thanks for the feedback. Right now we're in a situation where we definitely need to remove SwiftShader WebGL support but we're

Re: [blink-dev] Re: Intent to Ship: Animation.overallProgress

LGTM3 On 11/27/24 10:47 AM, Chris Harrelson wrote: LGTM2 On Wed, Nov 27, 2024 at 7:42 AM Rick Byers wrote: LGTM1 to ship in M133. It's nice to see the explainer and design improved based on TAG feedback, thank you for that! Rick On Tue, Nov 26, 2024 at 10:41 AM David Aw

Re: [blink-dev] Re: Intent to Ship: Nested pseudo elements styling

https://github.com/w3c/csswg-drafts/issues/4456 resolved to allow multiple pseudo-elements in getComputedStyle. I think it would be good to ship that ideally in the same release as this, or at least not much later. -- You received this message because you are subscribed to the Google Groups "b

Re: [blink-dev] Re: Intent to Ship: DOM `moveBefore()` method, for state-preserving atomic move

LGTM3 to ship once the spec PR has landed. Also, I'm really happy to see this new API coming to the web platform! Thanks to all that has made it happen! /Daniel On 2024-11-27 17:35, Rick Byers wrote: LGTM2 once the PR lands On Wed, Nov 27, 2024 at 11:16 AM Alex Russell wrote: Thanks

Re: [blink-dev] Intent to Ship: WebAssembly Memory64

LGTM3 On Tue, Nov 26, 2024 at 3:41 PM Mike Taylor wrote: > LGTM2 > On 11/26/24 10:15 AM, Rick Byers wrote: > > LGTM1, I'm excited to see this ship! > > I'm also terrified about how many of my tabs will want to use more than > 4GB of RAM at once for their AI models, but of course that is not a go

Re: [blink-dev] Re: Intent to Ship: DOM `moveBefore()` method, for state-preserving atomic move

LGTM2 once the PR lands On Wed, Nov 27, 2024 at 11:16 AM Alex Russell wrote: > Thanks for all of this. > > Would be good if we had a doc that explored the potential extension paths > for the existing APIs (arguments object as additional param?) vs. the > "larger bundle" path. I'm happy for this

Re: [blink-dev] Re: Intent to Ship: DOM `moveBefore()` method, for state-preserving atomic move

Thanks for all of this. Would be good if we had a doc that explored the potential extension paths for the existing APIs (arguments object as additional param?) vs. the "larger bundle" path. I'm happy for this specific API to ship assuming we have those options written up for the TAG (and API OW

Re: [blink-dev] Intent to Ship: Expose coarsened cross-origin renderTime in elment timing/LCP (regardless of TAO)

LGTM3 On Wed, Nov 27, 2024 at 11:13 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM2 > > On Friday, November 22, 2024 at 12:47:46 PM UTC+1 Noam Rosenthal wrote: > >> On Fri, Nov 22, 2024 at 6:21 AM Domenic Denicola >> wrote: >> >>> >>> >>> On Thu, Nov 21, 2024 at 6:07 PM Noam Ro

Re: [blink-dev] Intent to Ship: Expose coarsened cross-origin renderTime in elment timing/LCP (regardless of TAO)

LGTM2 On Friday, November 22, 2024 at 12:47:46 PM UTC+1 Noam Rosenthal wrote: > On Fri, Nov 22, 2024 at 6:21 AM Domenic Denicola > wrote: > >> >> >> On Thu, Nov 21, 2024 at 6:07 PM Noam Rosenthal >> wrote: >> >>> I think it would be worth asking for a standards-position specifically

Re: [blink-dev] Intent to Ship: Web Authentication API: PublicKeyCredential’s getClientCapabilities() method

LGTM2 On Fri, Nov 22, 2024 at 12:35 PM Mike Taylor wrote: > Thanks Andrii - I see that Mozilla is positive on the feature now, thanks > for requesting the review. > > And to Alex's request to call out FP risk - the spec does acknowledge it >

Re: [blink-dev] Intent to Ship: Explicit resource management (async)

LGTM2 On Thu, Nov 21, 2024 at 4:12 PM Mike Taylor wrote: > LGTM1 > On 11/21/24 6:44 PM, Rezvan Mahdavi Hezaveh wrote: > > Contact emails rez...@chromium.org, s...@chromium.org > > Explainer > https://github.com/tc39/proposal-explicit-resource-management/blob/main/README.md > > Specification http

Re: [blink-dev] Intent to Ship: Explicit resource management (sync)

LGTM2 On Thu, Nov 21, 2024 at 4:12 PM Mike Taylor wrote: > LGTM1 > On 11/21/24 6:44 PM, Rezvan Mahdavi Hezaveh wrote: > > Contact emails rez...@chromium.org, s...@chromium.org > > Explainer None > > Specification https://tc39.es/proposal-explicit-resource-management > > Summary > > This feature

Re: [blink-dev] Intent to Prototype: Clipboardchange event

Looks great, a clear improvement over polling. Thanks! Hopefully you can find APIs on non-Windows platforms to enable this. The explainer mentions polling the clipboard on MacOS but I'm not sure we'd want to do that in Chromium, would we? Perhaps it would be better to not expose the API on platfor

Re: [blink-dev] Re: Intent to Ship: Multiple import maps

LGTM3 On Fri, Nov 22, 2024 at 12:32 PM Mike Taylor wrote: > LGTM2 > On 11/20/24 9:03 PM, Domenic Denicola wrote: > > With my HTML editor hat on, I disagree with Alex's characterization of > this feature as under-specified, as well as his specific technical points > of feedback. I encourage him t

Re: [blink-dev] Intent to Experiment: ServiceWorkerAutoPreload

LGTM to experiment M131-M136. On Thu, Nov 21, 2024 at 11:12 PM Shunya Shishido wrote: > Contact emails > > sisidov...@chromium.org > > Explainer > > https://github.com/explainers-by-googlers/service-worker-auto-preload > > Specification > > None yet, we’ll write one after the experiment. > > Sum

Re: [blink-dev] Re: Intent to Ship: CSS Scroll State Container Queries

LGTM3 Is anyone looking into why the tests have harness errors on non-chromium browsers? Is that a bug in the test failing to fail properly? Rick On Wed, Nov 27, 2024 at 10:48 AM Chris Harrelson wrote: > LGTM2 > > On

Re: [blink-dev] Re: Intent to Ship: CSS Scroll State Container Queries

LGTM2 On Sun, Nov 24, 2024 at 7:22 AM Mike Taylor wrote: > LGTM1 > On 11/21/24 4:12 AM, Rune Lillesveen wrote: > > On Wed, Nov 13, 2024 at 10:38 AM Rune Lillesveen > wrote: > >> Four issues are opened against the spec: >> >> https://github.com/w3c/csswg-drafts/issues/11181 >> https://github.com

Re: [blink-dev] Re: Intent to Ship: Animation.overallProgress

LGTM2 On Wed, Nov 27, 2024 at 7:42 AM Rick Byers wrote: > LGTM1 to ship in M133. > > It's nice to see the explainer and design improved based on TAG feedback, > thank you for that! > > Rick > > On Tue, Nov 26, 2024 at 10:41 AM David Awogbemila > wrote: > >> >> >> On Tue, Nov 26, 2024 at 10:35 A

Re: [blink-dev] Re: Intent to Ship: Animation.overallProgress

LGTM1 to ship in M133. It's nice to see the explainer and design improved based on TAG feedback, thank you for that! Rick On Tue, Nov 26, 2024 at 10:41 AM David Awogbemila wrote: > > > On Tue, Nov 26, 2024 at 10:35 AM David Awogbemila > wrote: > >> Contact emailsawogbem...@google.com >> >> Ex

Re: [blink-dev] Intent to Extend Deprecation Trial (Again): Partitioning Storage, Service Workers, and Communication APIs

LGTM to extend this DT for another 6 milestones. On Tue, Nov 26, 2024 at 12:00 PM Ari Chivukula wrote: > Contact emails > > aric...@chromium.org, miketa...@chromium.org > > Explainer > > > https://github.com/wanderview/quota-

Re: [blink-dev] Re: Concerns over removal of SwiftShader fallback

According to https://issues.chromium.org/40277080, I believe geoffl...@chromium.org should be able to help you. On Wed, Nov 27, 2024 at 4:22 PM 'Ashley Gullen' via blink-dev < blink-dev@chromium.org> wrote: > Hi folks, it's been a week, is anyone from the relevant team able to > review this and r

Re: [blink-dev] Intent to Ship: FedCM authorization features (fka Bundle 6: Continuation API, Parameters API, Fields API, Multiple configURLs, Custom account labels)

LGTM2 On Wed, Nov 27, 2024 at 9:40 AM Vladimir Levin wrote: > Thank you for the explanation! > > LGTM1 > > On Mon, Nov 25, 2024, 1:53 p.m. Christian Biesinger < > cbiesin...@chromium.org> wrote: > >> >> >> On Mon, Nov 25, 2024 at 12:47 PM Vladimir Levin >> wrote: >> >>> Hey Christian, >>> >>> T

[blink-dev] Re: Concerns over removal of SwiftShader fallback

Hi folks, it's been a week, is anyone from the relevant team able to review this and respond? Best regards Ashley On Wed, 20 Nov 2024 at 16:54, Ashley Gullen wrote: > Hi Blink developers, > > I am concerned about this entry on Chrome Platform Status "Remove > SwiftShader fallback", currently s

Re: [blink-dev] Intent to Ship: Freezing on Energy Saver

I evaluated this intent relative to our compat principles and overall think you've done an excellent job mitigating the compat risks. In particular the user controls, developer-influencable heuristics and enterprise opt-out seem likely to be significant mitigations. I'

Re: [blink-dev] Intent to Ship: FedCM authorization features (fka Bundle 6: Continuation API, Parameters API, Fields API, Multiple configURLs, Custom account labels)

Thank you for the explanation! LGTM1 On Mon, Nov 25, 2024, 1:53 p.m. Christian Biesinger wrote: > > > On Mon, Nov 25, 2024 at 12:47 PM Vladimir Levin > wrote: > >> Hey Christian, >> >> Thank you for your reply. Additional questions below. >> >> On Fri, Nov 22, 2024 at 7:00 PM Christian Biesing