Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Non API OWNER here, but when looking through this feature I noticed that there are no tests for it. This line in reporting_browsertest.cc dis

Re: [blink-dev] Re: Intent to Ship: CSP require-sri-for for scripts

Thanks for reviewing!! In discussions with Mozilla folk, we eventually landed on a very different API shape , to enable them to expand the concept of "integrity policy", rather than doing this as a one-off CSP

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Thanks Issack. I appreciate you making it a priority to stabilize them. However, I would not have approved knowing what I know now - the advice would have been "please fix the tests and come back and report." What is the downside to disabling until we're in that state? On 3/27/25 4:57 PM, 'Iss

[blink-dev] Intent to Ship: CapturedSurfaceResolution

Contact emails agpa...@google.com, gui...@chromium.org Explainer https://github.com/guidou/mediacapture-extensions/blob/main/explainer-pixels.md Specification https://w3c.github.io/mediacapture-screen-share/#dfn-screenpixelratio Summary Expose pixel ratio of the captured surface while screen

[blink-dev] Intent to Prototype: Proofreader API

Contact emails queeniezh...@google.com, yaejee...@google.com Explainer https://github.com/explainers-by-googlers/proofreader-api/blob/main/README.md Specification None Summary A JavaScript API for proofreading input text with suggested corrections, backed by an AI language model. Blink c

[blink-dev] Intent to Prototype: Source phase imports

Contact emails lpardosix...@microsoft.com, s...@google.com Explainer None Specification https://arai-a.github.io/ecma262-compare/?pr=3492 Summary introduces the `import source` and `import.source` syntax. It allows modules to be imported as a representation of their compiled source, when th

Re: [blink-dev] Intent to Ship: WebAssembly Branch Hints

LGTM2 On 3/26/25 9:37 PM, Domenic Denicola wrote: Thanks for the answers! LGTM1. On Wed, Mar 26, 2025 at 7:25 PM Emanuel Ziegler wrote: Ah, I looked in the wrong "binary" rendering of the spec. This is the correct link: https://webassembly.github.io/branch-hinting/metadata/code/

Re: [blink-dev] Intent to Ship: RegExp.escape

It seems like shipped in 136; should we update the milestone if so? https://chromiumdash.appspot.com/commit/bb205a92ead761e2532c07f87c3c0f9223f69112 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving e

Re: [EXTERNAL] Re: [blink-dev] Intent to Remove: SwiftShader Fallback

Hi Rick, AFAIK it's only Windows, but currently reaching out to see if it's different for our distributors in Europe. Matt On Monday, March 24, 2025 at 10:38:19 AM UTC-7 Rick Byers wrote: > Thanks for chiming in Matt. Is the scenario you described Windows-only (in > which case we should be goo

[blink-dev] Re: Intent to Ship: WebGPU: GPUAdapterInfo isFallbackAdapter attribute

LGTM1 On Monday, March 24, 2025 at 10:13:11 AM UTC-4 François Beaufort wrote: > Contact emailsfbeauf...@google.com > > ExplainerThe GPUAdapter isFallbackAdapter boolean attribute currently > shipped in Chrome browser only does not allow libraries that take > user-provided GPUDevice objects from

[blink-dev] Re: I2P&S: Strict Same Origin Policy for Storage Access API

Is it a correct reading that that it's roughly 9% of 0.08% of pageloads that will be affected? That still seems large. Can you speak to the nature of the breakage? Specifically, do the sites that currently use it become unusable or is it a milder change from that? On the process side, do you mi

Re: [blink-dev] Intent to Ship: WebAssembly Branch Hints

Thank you all! FYI: we decided to only ship with M137 to give the feature a little more time in staged mode. While we don't foresee any problems, there is also no harm in waiting another 4 weeks. I have adjusted the target milestone in the feature accordingly for transparency. On Thu, Mar 27, 202

[blink-dev] Re: Intent to Ship: HSTS Tracking Prevention

I am updating here on behalf of Steven since he is OOO. We have updated the chrome status gates . On Monday, March 24, 2025 at 1:53:46 AM UTC-4 dom...@chromium.org wrote: > Can you request privacy, WP security, enterprise, debuggability, and

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Thanks Dom - that's not a great scenario that I didn't understand when approving. Issack, what is the plan for tests? Are they in progress, or should we unship/not ship the feature until they're ready? On 3/27/25 4:26 PM, Dominic Farolino wrote: Non API OWNER here, but when looking through th

Re: [blink-dev] Intent to Ship: WebAssembly Branch Hints

LGTM3 On Thu, Mar 27, 2025 at 7:54 AM Mike Taylor wrote: > LGTM2 > On 3/26/25 9:37 PM, Domenic Denicola wrote: > > Thanks for the answers! LGTM1. > > On Wed, Mar 26, 2025 at 7:25 PM Emanuel Ziegler > wrote: > >> Ah, I looked in the wrong "binary" rendering of the spec. This is the >> correct li

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Hi Dom and Mike, I have made multiple attempts to debug and resolve the flakiness of these tests throughout the development of this feature, and that effort is still in progress. As pointed out, we do have tests, but landing them as enabled has been challenging due to long-standing flakiness i

Re: [blink-dev] Re: Intent to Ship: Auto-generated view transition names

> > > > *Until this feature (correct me if I'm wrong), adding a unique ID to an > element was safe. With this feature, that's no longer the case.* > > > This seems like a worthwhile question to bring back to the TAG and/or the > CSSWG. Looking at the TAG review, it doesn't seem like it was discusse