Re: [blink-dev] Re: Intent to Ship: IndexedDB getAllRecords() and direction option for getAll()/getAllKeys()

LGTM2 On 7/31/25 8:43 p.m., Chris Harrelson wrote: Great! LGTM1 On Thu, Jul 31, 2025 at 11:34 AM 'Steve Becker' via blink-dev wrote: I merged the W3C IndexedDB getAllRecords() spec PR after reviews from Evan Stade (Microsoft Edge) and

Re: [EXTERNAL] [blink-dev] Intent to Ship: ServiceWorkerAutoPreload

LGTM3 On 7/30/25 4:23 p.m., Yoav Weiss (@Shopify) wrote: LGTM2 On Tuesday, July 29, 2025 at 2:01:24 AM UTC+2 dan...@microsoft.com wrote: Thanks for getting the spec PR landed, and for the clarifications on when the preload will be triggered. LGTM1. -- Dan On Sunday, July 27,

Re: [blink-dev] Intent to Ship: View Transitions: Inherit more animation properties

LGTM2 On 7/28/25 4:50 p.m., Vladimir Levin wrote: On Wed, Jul 23, 2025 at 11:32 AM Chris Harrelson wrote: LGTM1 On Mon, Jul 21, 2025 at 9:53 AM Chromestatus wrote: Contact emails vmp...@google.com Explainer None

Re: [blink-dev] Re: Intent to Experiment: SharedWorker on Android

LGTM On 7/17/25 11:27 p.m., 'Yoshisato Yanagisawa' via blink-dev wrote: Not sure why the Experiment Goals became empty, but let me copy contents from chromestatus. 2025年7月18日(金) 12:25 Chromestatus : Contact emails yyanagis...@google.com, dome...@chromium.org Ex

Re: [blink-dev] Intent to Experiment: Fetch retry (for keepalive fetches)

l (139-144). Thanks! Regards, Rakina On Fri, Jul 18, 2025, 02:07 Mike Taylor wrote: Thanks - you can request an OT for up to 6 milestones <https://www.chromium.org/blink/launching-features/#:~:text=An%20initial%20origin%20trial%20or%20experiment%20for%20a%20feature%20may%20only%20

Re: [blink-dev] Intent to Experiment: Fetch retry (for keepalive fetches)

hu, Jul 17, 2025 at 2:57 AM Mike Taylor wrote: Could you clarify which milestones you're requesting to experiment on? (Right now it just shows DevTrial on 139) On 7/16/25 11:31 a.m., Chromestatus wrote: Contact emails rak...@chromium.org, m...@chromium.o

Re: [blink-dev] Intent to Experiment: Fetch retry (for keepalive fetches)

Could you clarify which milestones you're requesting to experiment on? (Right now it just shows DevTrial on 139) On 7/16/25 11:31 a.m., Chromestatus wrote: Contact emails rak...@chromium.org, m...@chromium.org Explainer https://github.com/explainers-by-googlers/fetch-retry

Re: [blink-dev] Re: Intent to Ship: Controlled Frame API (available only to IWAs)

LGTM2 On 7/15/25 10:05 p.m., Domenic Denicola wrote: Thanks Dominic for that confirmation and your help reviewing. And thank you to Robbie for the impressive improvement to the API surface and the specification! This looks like a pretty good, webby API, with a nice detailed specification, wh

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Support font-feature-settings descriptor in @font-face rule

LGTM3 On 7/7/25 2:15 p.m., Alex Russell wrote: LGTM2 On Sunday, July 6, 2025 at 10:51:50 PM UTC-7 sejal...@microsoft.com wrote: Thank you Philip for your approval, font-variation-settings CL is also merged, I'll ship both of them together. --

Re: [blink-dev] Intent to Extend Experiment: Page-Embedded Permission Control

LGTM to keep experimenting given progress / conversations with other vendors. On 6/26/25 5:08 a.m., Chromestatus wrote: Contact emails andypa...@google.com, leminh...@google.com, vogelh...@google.com Explainer https://github.com/andypaicu/PEPC/blob/main/explainer.md

Re: [blink-dev] Intent to Experiment: Per-Function Explicit Compile Hints via Magic Comments

sition about the per-function extension of this proposal.) On Thu, Jun 5, 2025 at 2:36 PM Mike Taylor wrote: On 6/5/25 8:17 AM, 'Marja Hölttä' via blink-dev wrote: Contact emails ma...@google.com Explainer https://github.com/WICG/explicit-javas

Re: [blink-dev] Intent to Ship: View transition pseudos inherit animation-delay.

LGTM3 On 6/25/25 12:58 p.m., Vladimir Levin wrote: On Wednesday, June 25, 2025 at 11:28:33 AM UTC-4 Alex Russell wrote: LGTM2. Is there good documentation (e.g. in MDN) about which properties are inherited and from where? And how do CSS custom properties inherit in this parallel t

Re: [blink-dev] Re: Intent to Implement and Ship: Http cookie prefix

LGTM1, but conditioned on the spec work landing before shipping anything. On 6/25/25 1:00 a.m., Yoav Weiss (@Shopify) wrote: On Wed, Jun 25, 2025 at 4:18 AM Vladimir Levin wrote: On Thursday, June 19, 2025 at 9:48:37 AM UTC-4 Yoav Weiss wrote: Contact emailsyoavwe...@chromiu

Re: [blink-dev] Intent to Ship: CSS typed arithmetic

es as well. вторник, 17 июня 2025 г. в 20:51:00 UTC+2, Mike Taylor: On 6/16/25 8:13 AM, Chromestatus wrote: Contact emails sakha...@chromium.org Explainer None Specification https://www.w3.org/TR/css-values-4/#calc-type-checking <h

Re: [blink-dev] Intent to Experiment: Full frame rate render blocking attribute

LGTM to experiment from M139 to M144 (inclusive). On 6/15/25 11:04 p.m., 'Jiacheng Guo' via blink-dev wrote: Contact emails g...@google.com Explainer https://github.com/whatwg/html/issues/11070 Specification None

Re: [blink-dev] Re: Intent to Ship: Crash Reporting API: Specify crash-reporting to receive only crash reports

LGTM2 On 6/18/25 10:58 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Monday, June 16, 2025 at 6:25:02 AM UTC+2 Chromestatus wrote: Contact emails zhoupeng.1...@bytedance.com Explainer https://github.com/w3c/reporting/issues/263

Re: [blink-dev] Re: Intent to Implement and Ship: ReadableStreamBYOBReader Min Option

LGTM2 On 6/12/25 9:54 PM, Domenic Denicola wrote: LGTM1 On Friday, June 13, 2025 at 1:27:32 AM UTC+9 Sneha Agarwal wrote: Contact emails snehagar...@microsoft.com, stev...@microsoft.com Explainer None Note that the feature is somewhat documented at https://developer.mozilla

Re: [blink-dev] Intent to Ship: CSS typed arithmetic

On 6/16/25 8:13 AM, Chromestatus wrote: Contact emails sakha...@chromium.org Explainer None Specification https://www.w3.org/TR/css-values-4/#calc-type-checking Summary Typed arithmetic allows to write expressions in CSS such a calc(10em / 1px) or cal

Re: [blink-dev] Intent to Ship: Audio Level for RTC Encoded Frames

LGTM3 On 6/11/25 11:24 AM, Yoav Weiss (@Shopify) wrote: LGTM2 On Wednesday, June 11, 2025 at 5:24:05 PM UTC+2 Chris Harrelson wrote: LGTM1 On Mon, Jun 9, 2025 at 10:29 AM Chromestatus mailto:ad...@cr-status.appspotmail.com>> wrote: Contact emails gui...@

Re: [blink-dev] Intent to Ship: WebGPU 'core-features-and-limits'

to do to get his approved? Screenshot 2025-06-05 at 10.26.36.png On Tuesday, May 27, 2025 at 11:22:16 AM UTC-7 Mike Taylor wrote: Could you please request privacy, security, enterprise, and debuggability bits in your chromestatus entry? On 5/27/25 2:03 PM, Chromestatus wro

[blink-dev] Intent to Experiment: IP Protection in Incognito using published Masked Domain list

** *Contact emails* * miketa...@chromium.org, jhbrad...@google.com Explainer https://github.com/GoogleChrome/ip-protection/blob/main/README.md Specification None Summary IP Protection is

Re: [blink-dev] Re: Intent to Ship: Translator API

LGTM1 - the team has demonstrated a clear demand for this type of feature. I look forward to Mozilla shipping an alternate proposal - it seems to me that it's complementary and not in conflict with us shipping Translator now. On 6/3/25 10:27 AM, Mike Taylor wrote: On 6/3/25 9:27 AM, &#

Re: [blink-dev] Intent to Experiment: Per-Function Explicit Compile Hints via Magic Comments

On 6/5/25 8:17 AM, 'Marja Hölttä' via blink-dev wrote: Contact emails ma...@google.com Explainer https://github.com/WICG/explicit-javascript-compile-hints-file-based Specification There's no spec or draft spec for the per-function part yet - getting feedback on the input format is one of the

Re: [blink-dev] Intent to ship: WebGPU: 3D texture support for BC and ASTC compressed formats

On 6/4/25 3:41 AM, 'François Beaufort' via blink-dev wrote: Contact emails fbeauf...@google.com Explainer The "texture-compression-bc-sliced-3d" and "texture-compression-astc-sliced-3d" WebGPU features add respectively support for 3D textures using

Re: [blink-dev] Intent to Ship: Summarizer API

ey'd come. On Friday, May 23, 2025 at 11:46:53 PM UTC+2 Mike Taylor wrote: Thanks - I don't have any further concerns, but it seems useful to give Mozilla a few days to respond to the standards position ping before approving. On 5/23/25 12:53 PM, Daseul Lee wrote:

Re: [blink-dev] Re: Intent to Ship: Translator API

On 6/3/25 9:27 AM, 'Kagami Rosylight' via blink-dev wrote: > They haven’t given any negative signals on our proposed Translator API (nor official positive ones). You can consider Mozilla to be negative here. We plan to make it more clear in our counterproposal why we think it's better. If you

Re: [blink-dev] Re: Intent to Ship: Web app scope extensions

Multiple origins are possible, yeah: https://web-platform-tests.org/writing-tests/server-features.html#tests-involving-multiple-origins On 6/2/25 5:41 PM, 'Lu Huang' via blink-dev wrote: I thought about adding manual WPTs for this feature but it would require serving from 2 different origins in

Re: [blink-dev] Intent to Ship: WebXR Depth Sensing Performance Improvements

il.com> (of Meta who has commented on WebXR launches in the past) in case he can add any additional context here. On Mon, Jun 2, 2025 at 5:16 AM Mike Taylor wrote: On 5/30/25 12:47 PM, Alex Cooper wrote: > Can you say more why you think a TAG review isn

Re: [blink-dev] Intent to Ship: WebXR Depth Sensing Performance Improvements

expose the extensions we'd need there. So while technically the features are supported on Windows and Android, functionally they will only work on Android. Can you update the chromestatus entry with this info (see the "Platform Support Explanation" field)? Thanks. On Fri, Ma

Re: [blink-dev] Intent to Ship: WebXR Depth Sensing Performance Improvements

On 5/22/25 1:45 PM, Chromestatus wrote: Contact emails alcoo...@chromium.org Explainer https://github.com/immersive-web/depth-sensing/blob/main/explainer.md Specification https://immersive-web.github.io/depth-sensing Design docs https://docs.google.co

Re: [blink-dev] Intent to Ship: WebGPU 'core-features-and-limits'

Could you please request privacy, security, enterprise, and debuggability bits in your chromestatus entry? On 5/27/25 2:03 PM, Chromestatus wrote: Contact emails g...@google.com Explainer None Specification https://gpuweb.github.io/gpuweb/#core-features-and-limi

Re: [blink-dev] Intent to Ship: Speculation rules: target_hint field

Thanks, LGTM1. On 5/23/25 2:15 AM, Domenic Denicola wrote: On Wednesday, May 21, 2025 at 10:31:06 PM UTC+9 Mike Taylor wrote: On 5/20/25 6:06 AM, Chromestatus wrote: Contact emails robert...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main

Re: [blink-dev] Intent to Ship: CSS env variable for OS-level font scale

On 5/27/25 10:46 AM, Torne (Richard Coles) wrote: On Tue, 27 May 2025 at 05:48, Peter Birk Pakkenberg wrote: Hi, It is not entirely clear if this will also be enabled for WebView as part of the Android enablement. WebView has an API to explicitly set the text zoom

Re: [blink-dev] Intent to Ship: Summarizer API

, May 20, 2025 at 9:36 AM Daseul Lee wrote: Please see the inline replies below. On Fri, May 16, 2025 at 4:42 PM Mike Taylor wrote: On 5/16/25 12:14 PM, Daseul Lee wrote: Contact emails dome...@chromium.org, kenjibah...@chromium.org,

Re: [blink-dev] Intent to Ship: Add prefetchCache and prerenderCache to Clear-Site-Data header

On 5/22/25 1:16 AM, Domenic Denicola wrote: On Wed, May 21, 2025 at 9:48 PM Mike Taylor wrote: On 5/20/25 10:07 PM, Domenic Denicola wrote: (Feature-collaborator hat on, API owners hat off.) Thanks for sending this! A few minor corrections here, that it'd be good to

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Fire error event instead of throwing for CSP blocked worker

support message) and other seems to mark inline service worker as not supported. Don’t see that how that not supported mark was used. It seems to me that the most direct impact of the exception handlers is to allow code after it to continue. Liang *From:*Mike Taylor *Sent:* Wednesday, May 21

Re: [blink-dev] Intent to Ship: Speculation rules: target_hint field

On 5/20/25 6:06 AM, Chromestatus wrote: Contact emails robert...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main/triggers.md#window-name-targeting-hints Specification https://wicg.github.io/nav-speculation/speculation-rules.html

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Fire error event instead of throwing for CSP blocked worker

Thank you for doing this work! One small question below, but this generally seems like it will be safe to land. On 5/20/25 6:45 PM, 'Liang Zhao (REDMOND)' via blink-dev wrote: An update. https://chromestatus.com/metrics/feature/timeline/popularity/5356 now has list of urls. I’ve tested those

Re: [blink-dev] Intent to Ship: Add prefetchCache and prerenderCache to Clear-Site-Data header

On 5/20/25 10:07 PM, Domenic Denicola wrote: (Feature-collaborator hat on, API owners hat off.) Thanks for sending this! A few minor corrections here, that it'd be good to make to the ChromeStatus entry. On Wed, May 21, 2025 at 10:42 AM Chromestatus wrote: Contact emails

Re: [blink-dev] PSA: Changes to the fetch() option `targetAddressSpace`

Thanks for sending the PSA, Chris. On 5/20/25 7:00 PM, Chris Thompson wrote: Hello blink-dev@ -- As part of our work on Local Network Access restrictions (which is superseding a prior effort called Private Network Access

Re: [blink-dev] Intent to Ship: Summarizer API

On 5/16/25 12:14 PM, Daseul Lee wrote: Contact emails dome...@chromium.org, kenjibah...@chromium.org, m...@chromium.org, btri...@chromium.org, ds...@chromium.org, a...@chromium.org Explainer https://github.com/webmachinelearning/writing-assistance-apis/blob/main/README.md

Re: [blink-dev] Intent to Experiment: Prompt API

LGTM to experiment from M139 to M144 inclusive. On 5/16/25 3:18 AM, Domenic Denicola wrote: Contact emails a...@chromium.org, m...@chromium.org, btri...@chromium.org, dome...@chromium.org, kenjibah...@chromium.org Explainer https://github.com/webmachinelearning/prompt-api

Re: [blink-dev] Intent to Ship: Crash Reporting API: is_top_level & visibility_state

LGTM2 On 5/14/25 8:55 PM, Domenic Denicola wrote: LGTM1 On Thu, May 15, 2025 at 4:08 AM Dominic Farolino wrote: Thanks for pointing this oversight out! It's been addressed in the spec, and the impl  is up for r

Re: [blink-dev] PSA: HTMLFencedFrameElement.canLoadOpaqueURL() to be removed

On 5/9/25 6:21 PM, Shivani Sharma wrote: On Fri, May 9, 2025 at 4:25 PM Mike Taylor wrote: On 5/8/25 9:56 AM, Xiaochen Zhou wrote: The functionality of canLoadOpaqueURL() was replaced with navigator.canLoadAdAuctionFencedFrame() <https://wicg.github.io/turtled

Re: [blink-dev] Intent to Ship: CSS sibling-index() and sibling-count()

LGTM1 On 5/9/25 9:47 AM, Rune Lillesveen wrote: Contact emails futh...@chromium.org, se...@chromium.org Explainer https://github.com/w3c/csswg-drafts/blob/main/css-values-5/tree-counting-explainer.md Specification https://drafts.csswg.

Re: [blink-dev] Intent to Extend Experiment: Playout Statistics API for WebAudio

Thanks for the updates on progress. LGTM to extend from M137 to M139 inclusive. On 5/9/25 10:27 AM, 'Fredrik Hernqvist' via blink-dev wrote: Contact emails fhernqv...@google.com, o...@google.com, hongc...@google.com, agpa...@google.com, gui...@google.com Explainer https:

Re: [blink-dev] Intent to Ship: Pass 'Sec-Purpose: prefetch' header with

Before continuing the review, could you please request all the privacy, security, enterprise, etc bits in the chromestatus entry? On 5/12/25 2:32 PM, 'Steven Wei' via blink-dev wrote: domenic@ found the place in HTML spec that already mentioned this header for prefetch: Fetch Standard

Re: [blink-dev] Ready for Developer Testing: Modulepreload Referrer Header Fix

I suspect this is supposed to be an I2S (per https://chromium-review.googlesource.com/c/chromium/src/+/6509110/comments/da10e968_f515270f), but if "Ready for Developer Testing" is the correct stage - a feature flag for devs to flip and test would be useful. Could you clarify? Thanks On 5/8/25

Re: [blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

Given that Firefox has implemented this (Nightly-only ), as well as Safari (not landed yet? ), do we know why https://github.com/whatwg/html/pull/6362 hasn't been merged yet? On 5/12/25 11:23 AM

Re: [blink-dev] PSA: HTMLFencedFrameElement.canLoadOpaqueURL() to be removed

On 5/8/25 9:56 AM, Xiaochen Zhou wrote: The functionality of canLoadOpaqueURL() was replaced with navigator.canLoadAdAuctionFencedFrame() in 2023. Calling the canLoadOpaqueURL() API has resulted in a deprecation console warning

Re: [blink-dev] Re: Intent to Ship: CSS Custom Functions (@function)

Thanks for the updates. LGTM1 On 5/6/25 4:41 AM, Anders Hartvoll Ruud wrote: See updates inline: On Wed, Feb 26, 2025 at 10:10 PM Anders Hartvoll Ruud wrote: Note that this was targeting the M136 release, so we would have had another month to tweak this feature, and even a couple o

Re: [blink-dev] Intent to Ship: Deprecate GPUAdapter isFallbackAdapter attribute

LGTM2 On 5/2/25 5:33 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Fri, May 2, 2025 at 11:16 AM François Beaufort wrote: On Fri, May 2, 2025 at 11:09 AM Yoav Weiss (@Shopify) wrote: On Fri, May 2, 2025 at 10:55 AM 'François Beaufort' via blink-dev wrote:

Re: [blink-dev] Intent to Extend Experiment: Cookie Deprecation Label

LGTM to extend from 136 to 138 inclusive. On 5/1/25 12:21 PM, 'Josh Karlin' via blink-dev wrote: On Wed, Apr 30, 2025 at 11:45 AM Jxck wrote: What is the motivation for 3rd Parties to experiment Privacy Sandbox, Storage Access API etc etc alternates 3rd Party Cookies from point of

Re: [blink-dev] Intent to Experiment: Cache sharing for extremely-pervasive scripts

a heads-up. On Wed, Apr 30, 2025 at 11:29 AM Mike Taylor wrote: Yeah, probably. Jason, are you able to do some backend magic to convert the chromestatus type? On 4/30/25 10:33 AM, Patrick Meenan wrote: I'm hoping for 138 (code is in-flight now). I added 138 to the

Re: [blink-dev] Intent to Experiment: Cache sharing for extremely-pervasive scripts

eriment". The only stages that come after (or can be added) are shipping. Maybe because it's "No developer-facing change" for the feature type? On Wed, Apr 30, 2025 at 7:01 AM Mike Taylor wrote: Thanks Patrick. It will be interesting to learn how the exper

Re: [blink-dev] Intent to Ship: Support transactional batchUpdate() and disallow batch inner locks

LGTM3 On 4/30/25 11:24 AM, Yoav Weiss (@Shopify) wrote: LGTM2 On Wednesday, April 30, 2025 at 5:23:41 PM UTC+2 Chris Harrelson wrote: LGTM1 On Fri, Apr 25, 2025 at 1:16 PM Yao Xiao wrote: Intent to Ship: Support transactional batchUpdate() and disallow batch inner lo

Re: [blink-dev] Re: Intent to Implement and Ship: isSecurePaymentConfirmationAvailable API

So requesting a re-review from API OWNERS, thanks. Let me know if it needs to be 3x LGTM or just 1x :). On Wednesday, March 12, 2025 at 6:40:08 PM UTC-4 Mike Taylor wrote: On 3/10/25 10:12 AM, Stephen McGruer wrote: > It may change shape before finally shipping (in

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent color for accent-color property.

Or rather, LGTM2 On 4/30/25 7:06 AM, Mike Taylor wrote: Thanks, LGTM1 On 4/29/25 1:45 PM, Priya Palanisamy wrote: Hi Mike, Yes, the I2S proposes using the system accent color when the value is set to "auto". To clarify, "auto" is also the default option if n

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent color for accent-color property.

citly set, the form elements will automatically use the system accent color by default. Thanks, Priya ---- *From:* Mike Taylor *Sent:* Tuesday, April 29, 2025 7:46 AM *To:* Alex Russell ; blink-dev *Cc:* Chromestatus ; Alison Mah

Re: [blink-dev] Intent to Experiment: Cache sharing for extremely-pervasive scripts

en by most users multiple times within a browsing session (and within the update window for any of them). On Tue, Apr 29, 2025 at 10:52 AM Mike Taylor wrote: Hey Patrick, This sounds related to a previous experiment (https://groups.go

Re: [blink-dev] Intent to Experiment: Cache sharing for extremely-pervasive scripts

ely to be seen by most users multiple times within a browsing session (and within the update window for any of them). On Tue, Apr 29, 2025 at 10:52 AM Mike Taylor wrote: Hey Patrick, This sounds related to a previous experiment (https://groups.google.com/a/chromium.org/g/blink-de

Re: [blink-dev] Intent to Experiment: Cache sharing for extremely-pervasive scripts

Hey Patrick, This sounds related to a previous experiment (https://groups.google.com/a/chromium.org/g/blink-dev/c/9xWJK3IgJb4/m/SYLfUccOBgAJ) - could you describe how this experiment is similar or different (or perhaps builds upon the results from the previous experiment)? thanks, Mike On 4

Re: [blink-dev] Re: Intent to Ship: System accent color for accent-color property.

Just to clarify, this intent proposes to add an `auto` value to accept-color, that picks up the system accent-color. Do I have that right? On 4/28/25 2:15 PM, Alex Russell wrote: Hey Priya, Can we make sure to request explicit signals from WebKit? Thanks. LGTM1 modulo that nit. Best, Alex

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Support transform attribute on SVGSVGElement

s. I hope that does answer your questions but let me know if you need more clarification! Perfect, that's helpful - I appreciate the explanations. With Regards Divyansh *From:*Mike Taylor *Sent:* Wednesday, April 23, 2025 4:52 PM *To:* Divyansh Mangal *Cc:* blink-dev@chromium.org *Su

Re: [blink-dev] Intent to Ship: Support transform attribute on SVGSVGElement

On 4/22/25 9:54 AM, 'Divyansh Mangal' via blink-dev wrote: *Contact emails* dman...@microsoft.com *Explainer* None *Specification* https://www.w3.org/TR/SVG2/struct.html#SVGElement *Summary* This feature enables the application of transformation properties—such as scaling, rotation, t

Re: [blink-dev] Intent to Implement and Ship: Integrity Policy for scripts

LGTM1 On 4/23/25 5:12 AM, Yoav Weiss (@Shopify) wrote: Contact emails yoavwe...@chromium.org Explainer https://github.com/w3c/webappsec-subresource-integrity/pull/133 Specification https://github.com/w3c/webappsec-subresource-integrity/pull/133 Summary

Re: [blink-dev] Intent to Ship: Ignore Letter Spacing in Cursive Scripts

On 4/21/25 11:20 PM, 'Sejal Anand' via blink-dev wrote: Contact emails sejalan...@microsoft.com Explainer None Specification https://www.w3.org/TR/css-text-3/#cursive-tracking Summary This feature adds lo

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

#x27;d need to revamp the implementation and spec. I'll let y'all know when it's time to reapprove (I can do that as a separate intent, if that would be more convenient) On Wed, Mar 26, 2025 at 11:02 AM Chris Harrelson wrote: LGTM3 On Tue, Mar 25,

Re: [blink-dev] Implement and Ship: Blob URL Partitioning: Fetching/Navigation

I am recused from giving LGTMs on this one, but the new use counters and other mitigations (enterprise policy, finch killswitch, chrome://flags entry) suggest to me that the risk is low, and if we get it wrong, we can undo the change. On 4/18/25 4:39 PM, Andrew Williams wrote: Hi blink-dev,

Re: [blink-dev] Re: Intent to Extend Experiment: Summarizer API

LGTM to extend from 137 to M139 inclusive. On 4/16/25 6:35 PM, Ayu Ishii wrote: Hi Alex! Yes, here is some positive quantitative feedback we've gathered via surv

Re: [blink-dev] Intent to Ship: WebGPU: GPUTextureView for externalTexture binding

at as well. From talking with the Mozilla engineers working on WebGPU, this would require our API owners to talk with their standard folks to come to some agreement there (though I don't know who that might be so I can't start an email thread). On Saturday, April 12, 2025 at 1:45:5

Re: [blink-dev] Intent to Ship: WebGPU: GPUTextureView for externalTexture binding

Is there a place to find meeting minutes where Mozilla stated this? Agree with Domenic that it would be good to have a stable reference. On 4/11/25 10:16 AM, Yoav Weiss (@Shopify) wrote: LGTM2 On Fri, Apr 11, 2025 at 7:09 AM Domenic Denicola wrote: LGTM1. Although, it would be good to

Re: [blink-dev] Intent to Ship: JavaScript Promise Integration

LGTM3 On 4/9/25 8:35 AM, Chris Harrelson wrote: LGTM2 On Wed, Apr 9, 2025 at 8:26 AM Philip Jägenstedt wrote: LGTM1, very exciting to see this ship! There are some apparent failures in https://wpt.fyi/results/wasm/jsapi/jspi, but this seems to be because of https://gith

Re: [blink-dev] Re: Intent to Ship: Accept-Language Reduction (HTTP-only)

roposing to ship this to HTTPS? No, this is just shorthand for not touching the JS APIs, but only the Accept-Language header sent over HTTP (or HTTPS). Regards, Frank On Wednesday, April 9, 2025 at 9:01:44 AM UTC-7 Mike Taylor wrote: Also, thanks for the offer to help with the appcompat a

Re: [blink-dev] Re: Intent to Ship: Accept-Language Reduction (HTTP-only)

with an initial assessment too :) Thanks, Peter On Tue, Apr 8, 2025 at 4:21 PM Mike Taylor wrote: We do intend to follow suit there once we learn we can ship this and its compatible with the web. It seems nice to separate web compat problems from app comp

Re: [blink-dev] Intent to Deprecate and Remove: Remove auto-detection of ISO-2022-JP charset in HTML

LGTM1 to just remove this outright. I looked at the 8 sites listed on chromestatus, and of those only 2 seem to be affected in a meaningful way. Would you mind trying to do outreach to those 2 sites and let them know how they can fix this ahead of the change? https://bbb.asahi-net.or.jp/ - m

Re: [blink-dev] Intent to Ship: Protected Audience: Creative scanning via BYOS/V1 trusted scoring signals

On 3/28/25 1:06 PM, 'Orr Bernstein' via blink-dev wrote: Contact emails o...@google.com, pauljen...@chromium.org, morlov...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1406 Specifically, see addition of creativeScanningMeta

Re: [blink-dev] Re: Intent to Ship: Accept-Language Reduction (HTTP-only)

We do intend to follow suit there once we learn we can ship this and its compatible with the web. It seems nice to separate web compat problems from app compat problems, if we can. On 4/8/25 6:48 AM, Peter Beverloo wrote: Hi Victor - you write that the feature is supported on all of Blink's pl

Re: [blink-dev] Intent to Extend Experiment: Digital Credential API

LGTM to extend from M137 to M139 inclusive. On 4/7/25 9:34 AM, Chromestatus wrote: Contact emails rby...@chromium.org, g...@chromium.org, ma...@chromium.org, ashimaar...@google.com Explainer https://github.com/WICG/digital-credentials/blob/main/explainer.md Spec

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

On 3/25/25 1:39 PM, Yoav Weiss (@Shopify) wrote: On Tue, Mar 25, 2025 at 10:37 AM Vladimir Levin wrote: I'm not convinced this is a huge footgun. Yes, it's a convenience value that allows auto matching in MPA where there is no other way to automatically match without changes to th

Re: [blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

On 3/25/25 11:04 AM, Liam Brady wrote: > Note: reading explainer diffs is not great UX. Ack. I'll avoid linking explainer diffs directly in the future. This section in the FFAR explainer doc sh

Re: [blink-dev] Intent to Prototype: Limiting Access to Local Fonts

That seems to be covered in a few places in the explainer, but most clearly at https://github.com/explainers-by-googlers/limiting-local-fonts-access?tab=readme-ov-file#limiting-to-local-fonts-will-break-my-application-what-should-i-do On 4/3/25 4:32 AM, 'Ashley Gullen' via blink-dev wrote: Pres

Re: [blink-dev] Intent to Extend Experiment: Origin Trial for Third Party Cookie Deprecation

Quick question on timing: The last extension was approved from M131 to M133, which means the experiment has been expired since 134 (which is the current stable release, with M135 scheduled to start rolling out ~tomorrow. If you request to extend to 136, you're going to be a bit "shortchanged"

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

link-dev wrote: Thank you all for the reviews! :) On Tuesday, March 18, 2025 at 7:32:56 PM UTC-7 vmp...@chromium.org wrote: LGTM3 On Tuesday, March 18, 2025 at 8:47:30 AM UTC-4 Mike Taylor wrot

Re: [blink-dev] Intent to Extend Experiment: Origin Trial for Third Party Cookie Deprecation

to share in the next several weeks. Thanks, Joshua On Mon, Mar 31, 2025 at 1:52 PM Mike Taylor wrote: Quick question on timing: The last extension was approved from M131 to M133, which means the experiment has been expired since 134 (which is the current stable release, with M1

Re: [blink-dev] Intent to Ship: view-transition-name: auto

LGTM1, even if the name changes from `auto` to something else. Adding or removing an ID to a dom element (or a class even) may always carry the risk of breaking behavior or styling in a page. Perhaps this is more likely in certain types of apps, perhaps not. I don't think we're treading new gr

[blink-dev] Intent to Prototype: User-Agent Client Hints "ch-ua-high-entropy-values" permissions policy

*Contact emails* *** miketa...@chromium.org Explainer See Motivation below. Specification https://wicg.github.io/ua-client-hints/#ch-ua-high-entropy-values Summary Adds support for a

Re: [blink-dev] Intent to Ship: FedCM multi IDP in single get(), and remove add another account, in passive mode

LGTM3 On 4/2/25 10:14 AM, Daniel Bratell wrote: LGTM2 /Daniel On 2025-03-31 17:28, Rick Byers wrote: LGTM1 FWIW I've always considered it a bug that FedCM only supported a single IDP at a time. I know there are complex UX design issues to address and a couple small tweaks in the API. The

Re: [EXTERNAL] [blink-dev] Intent to Ship: Selection API getComposedRanges and direction

LGTM2 On 4/1/25 10:23 PM, Vladimir Levin wrote: LGTM1 On Wednesday, March 26, 2025 at 5:38:45 PM UTC-4 Di Zhang wrote: The WPT tests failing is mostly because Safari still using the old specification for getComposedRanges() syntax. This change was resolved in September 2024: ht

Re: [blink-dev] Intent to Ship: Accept-Language Reduction (HTTP-only)

On 4/1/25 5:00 PM, Jeffrey Yasskin wrote: Have you proposed that a standards body adopt this into a working group of some sort? Especially since Safari is doing something similar, it seems like the WHATWG might be willing to adopt this into the Fetch standard. I think it may be possible to sta

Re: [blink-dev] Re: Intent to Ship: view-transition-name: match-element

LGTM1 On 3/31/25 3:38 PM, Vladimir Levin wrote: On Mon, Mar 31, 2025 at 3:27 PM Vladimir Levin wrote: Contact emails vmp...@chromium.org, nrosent...@chromium.org Explainer None The explainer is here: https://github.com/WICG/view-transitions/blob/main

Re: [blink-dev] Re: Intent to Ship: CSS if() function

Does our implementation match these new edits? On 3/26/25 11:32 AM, 'Munira Tursunova' via blink-dev wrote:  Thank you for your replies.  Some of these changes (which are somewhat significant) have been discussed last week, like [1] for a concrete example, and the spec hasn't even b

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

On 3/31/25 4:44 AM, Corentin Wallez wrote: On Friday, March 28, 2025 at 1:57:08 PM UTC+1 Mike Taylor wrote: LGTM3 On 3/28/25 5:44 AM, TAMURA, Kent wrote: LGTM2 On Thu, Mar 27, 2025 at 6:43 PM Yoav Weiss (@Shopify) wrote: LGTM1 On Monday, March 24

Re: [blink-dev] Intent to Ship: AudioContext Interrupted State

LGTM3 - it's nice to see cross-vendor support for this. On 3/28/25 5:35 AM, TAMURA, Kent wrote: LGTM2. On Thu, Mar 27, 2025 at 12:37 AM Chris Harrelson wrote: LGTM1 On Tue, Mar 25, 2025 at 1:57 PM Chromestatus wrote: Contact emails gabrielbr...@micr

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

LGTM3 On 3/28/25 5:44 AM, TAMURA, Kent wrote: LGTM2 On Thu, Mar 27, 2025 at 6:43 PM Yoav Weiss (@Shopify) wrote: LGTM1 On Monday, March 24, 2025 at 10:13:11 AM UTC-4 François Beaufort wrote: Contact emails fbeauf...@google.com

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

ld be a priority, ideally before hitting stable. Please let me know if I'm missing something! On Wed, Mar 19, 2025 at 2:10 PM 'Issack John' via blink-dev wrote: Thank you all for the reviews! :) On Tuesday, March 18, 2025 at 7:32:56 PM UTC-7 vmp...@ch

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

ev wrote: Thank you all for the reviews! :) On Tuesday, March 18, 2025 at 7:32:56 PM UTC-7 vmp...@chromium.org wrote: LGTM3 On Tuesday, March 18, 2025 at 8:47:30 AM UTC-4 Mike Taylor wrote:  LGTM2 - I see that Mozilla has proposed a positive

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: Automatic beacon cross-origin data support (M135)

subframe doesn't want to provide data to be used, but still wants an automatic beacon to be sent out when it performs a top-level navigation. On Wed, Mar 26, 2025 at 9:41 AM Mike Taylor wrote: On 3/25/25 11:04 AM, Liam Brady wrote: > Note: reading explainer diffs is not grea

Re: [blink-dev] Intent to Ship: Protected Audience (B&A): Support multiple sellers in navigator.getInterestGroupAdAuctionData

LGTM2 On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote: Yes, it's just a performance/ergonomics change. Developers could previously get the same effect by calling the existing API multiple times. On Wed, Mar 26, 2025 at 11:35 AM Chris Harrelson wrote: Sounds fine - a performanc

  1   2   3   4   5   6   7   8   9   10   >