Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Thank you, everyone! On Tuesday, September 9, 2025 at 4:11:08 PM UTC-7 Chris Harrelson wrote: > LGTM3 > > On Tue, Sep 9, 2025 at 12:49 PM Daniel Bratell wrote: > >> LGTM2 >> >> /Daniel >> On 2025-09-08 20:19, Alex Russell wrote: >> > Thanks so much for doing that. >> >> LGTM1 >> >> On Wednesday

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Back to the original intent, the only outstanding question I see is the status of the WPTs. I see the CL has added 4 WPTs

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

LGTM3 On Tuesday, September 9, 2025 at 10:15:17 AM UTC-4 Chris Harrelson wrote: > LGTM2 > > On Tue, Sep 9, 2025, 3:50 AM Yoav Weiss (@Shopify) > wrote: > >> LGTM1 >> >> The lack of any problematic sites in the HTTPArchive sample as well as >> lack of Firefox/Safari issues on that front makes

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

LGTM3 On Tue, Sep 9, 2025 at 12:49 PM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2025-09-08 20:19, Alex Russell wrote: > > Thanks so much for doing that. > > LGTM1 > > On Wednesday, September 3, 2025 at 7:49:21 PM UTC+1 Brandon Jones wrote: > >> Hey Alex! >> >> An updated explainer is now ho

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

LGTM2 On Tue, Sep 9, 2025, 3:50 AM Yoav Weiss (@Shopify) wrote: > LGTM1 > > The lack of any problematic sites in the HTTPArchive sample as well as > lack of Firefox/Safari issues on that front makes me hopeful. > Please stay tuned to bug reports as well as metrics while Finching this. > > On Mon

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

LGTM2 /Daniel On 2025-09-08 20:19, Alex Russell wrote: Thanks so much for doing that. LGTM1 On Wednesday, September 3, 2025 at 7:49:21 PM UTC+1 Brandon Jones wrote: Hey Alex! An updated explainer is now hosted at https://github.com/gpuweb/gpuweb/blob/main/proposals/primitive-ind

Re: [blink-dev] Intent to Ship: FedCM—Support Structured JSON Responses from IdPs

LGTM1 This seems like a small yet useful addition. On Sat, Sep 6, 2025 at 5:51 AM Chromestatus wrote: > Contact emails sureshpo...@microsoft.com > > Explainer > https://github.com/w3c-fedid/idp-registration/issues/13#issuecomment-3254858070 > > Specification https://github.com/w3c-fedid/FedCM/p

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

LGTM1 The lack of any problematic sites in the HTTPArchive sample as well as lack of Firefox/Safari issues on that front makes me hopeful. Please stay tuned to bug reports as well as metrics while Finching this. On Monday, September 8, 2025 at 11:15:38 AM UTC+2 Steinar H Gunderson wrote: > On T

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

LGTM3 On Mon, Sep 8, 2025 at 11:31 AM 'Dan Clark' via blink-dev < blink-dev@chromium.org> wrote: > LGTM2, also conditional on tests being added. Thanks for getting position > requests filed (https://github.com/mozilla/standards-positions/issues/1295, > https://github.com/WebKit/standards-position

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

LGTM2, also conditional on tests being added. Thanks for getting position requests filed (https://github.com/mozilla/standards-positions/issues/1295, https://github.com/WebKit/standards-positions/issues/547). -- Dan On Wednesday, September 3, 2025 at 7:16:05 AM UTC-7 sligh...@chromium.org wrote

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Thanks so much for doing that. LGTM1 On Wednesday, September 3, 2025 at 7:49:21 PM UTC+1 Brandon Jones wrote: > Hey Alex! > > An updated explainer is now hosted at > https://github.com/gpuweb/gpuweb/blob/main/proposals/primitive-index.md. > It's still fairly brief because this is a relatively

Re: [blink-dev] Intent to Ship: Range syntax for style container queries and if()

Thank you! https://github.com/w3c/csswg-drafts/issues/12236 > This is now specified and addressed in

Re: [blink-dev] Intent to Ship: Removal of X-Requested-With in WebView

Sorry if this is not the right place to ask but I'm curious what the status of this is? I'm on WebView 141 and it is still sending the X-Requested-With header. On Wednesday, April 19, 2023 at 2:55:38 PM UTC-5 Chris Harrelson wrote: > LGTM3 > > On Wed, Apr 12, 2023 at 1:14 AM Peter Birk Pakkenb

Re: [blink-dev] Intent to Ship: Mobile and desktop parity for select element rendering modes

> Any plans to add a built-in search/type-to-filter field into the rendered widget (either popup or in-page) when there are more than one "page"/scroll of options? I've been discussing this capability here: https://github.com/openui/open-ui/issues/847 On Thu, Sep 4, 2025 at 1:13 PM PhistucK wrot

[blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

Contact emails se...@chromium.org Explainer None Specification https://drafts.csswg.org/cssom/#dom-window-getcomputedstyle Summary When iterating over window.getComputedStyle(element) in Chromium, there is a bug where it forgets to include any custom properties set on the element. (length(

[blink-dev] Intent to Ship: FedCM—Support Structured JSON Responses from IdPs

Contact emails sureshpo...@microsoft.com Explainer https://github.com/w3c-fedid/idp-registration/issues/13#issuecomment-3254858070 Specification https://github.com/w3c-fedid/FedCM/pull/771 Summary Allows Identity Providers (IdPs) to return structured JSON objects instead of plain strings to

Re: [blink-dev] Intent to Ship: Mobile and desktop parity for select element rendering modes

LGTM1. The consistent behavior is reasonable, and the compatibility risk looks very small. On Fri, Sep 5, 2025 at 2:42 AM Joey Arhar wrote: > Contact emailsjar...@chromium.org > > Explainer > https://github.com/whatwg/html/issues/8189#issuecomment-2877242732 > > Specificationhttps://github.com

Re: [blink-dev] Intent to Ship: Mobile and desktop parity for select element rendering modes

Sounds nice. Any plans to add a built-in search/type-to-filter field into the rendered widget (either popup or in-page) when there are more than one "page"/scroll of options? ☆*PhistucK* On Thu, Sep 4, 2025 at 6:42 PM Joey Arhar wrote: > Contact emailsjar...@chromium.org > > Explainer > https

[blink-dev] Intent to Ship: Mobile and desktop parity for select element rendering modes

Contact emailsjar...@chromium.org Explainerhttps://github.com/whatwg/html/issues/8189#issuecomment-2877242732 Specificationhttps://github.com/whatwg/html/pull/11460 Summary By using the size and multiple attributes, the select element can be rendered as an in-page listbox or a button with a pop

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

You got it right! And no, there's no need for the heavier-weight about:flags for these sorts of small changes. On Thu, Sep 4, 2025 at 1:04 AM Helmut Januschka wrote: > so it is a FinchFlag `ModulePreloadReferrer` and it is not listed in > about_flags.cc - hope i filled out the correct field in

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

On Thu, Sep 4, 2025 at 11:20 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails se...@chromium.org > > Explainer None > > Specification https://drafts.csswg.org/cssom/#dom-window-getcomputedstyle > > Summary > > When iterating over window.getComputedStyle(element) in Chromi

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

I have made public copies of the sheets and proposed updates in the doc. Also linked below. Steinar and I analyzed about half of the sites each, so I can say something about the findings. html2image: - https://docs.google.com/spreadsheets/d/1w2RuTpw3KG5zFvk9dmRlK-cS38MydyErnsUJzJ12AW8/edi

[blink-dev] Intent to Ship: Support `download` attribute in SVG element

Contact emails ragsha...@microsoft.com Explainer None Specification https://svgwg.org/svg2-draft/linking.html#InterfaceSVGAElement Summary This feature introduces support for the download attribute on the SVGAElement interface in Chromium, aligning with the SVG 2 specification. The download

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

On Thu, Sep 4, 2025 at 3:52 PM Yoav Weiss (@Shopify) wrote: > > > On Thursday, September 4, 2025 at 2:47:24 PM UTC+2 Steinar H Gunderson > wrote: > > On Thu, Sep 04, 2025 at 02:34:08PM +0200, Yoav Weiss (@Shopify) wrote: > > Thanks for the description of the issue! > > Is there any way to estimat

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

On Thursday, September 4, 2025 at 2:47:24 PM UTC+2 Steinar H Gunderson wrote: On Thu, Sep 04, 2025 at 02:34:08PM +0200, Yoav Weiss (@Shopify) wrote: > Thanks for the description of the issue! > Is there any way to estimate how many sites will be impacted by the > slowness here? Do we have a

Re: [blink-dev] Intent to Ship: Custom property enumeration in getComputedStyle()

On Thu, Sep 04, 2025 at 02:34:08PM +0200, Yoav Weiss (@Shopify) wrote: > Thanks for the description of the issue! > Is there any way to estimate how many sites will be impacted by the > slowness here? Do we have a use counter of some sorts? For ones that are > impacted, how much slower do they beco

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Hey Alex! An updated explainer is now hosted at https://github.com/gpuweb/gpuweb/blob/main/proposals/primitive-index.md. It's still fairly brief because this is a relatively small feature. --Brandon On Wed, Sep 3, 2025 at 7:13 AM Alex Russell wrote: > Thanks for this, Brandon. > > As you know,

[blink-dev] Intent to Ship: :target-before and :target-after pseudo-classes

Contact emailssakha...@chromium.org ExplainerBeing able to select scroll markers before/after the target one allows to e.g. highlight the progress of the scroller by styling the already viewed scroll markers. Specification https://drafts.csswg.org/css-overflow-5/#active-before-after-scroll-marker

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

so it is a FinchFlag `ModulePreloadReferrer` and it is not listed in about_flags.cc - hope i filled out the correct field in chromestatus should it be listed in about_flags for webdevs to enable? Daniel Bratell schrieb am Mittwoch, 3. September 2025 um 17:17:28 UTC+2: > Great! > > Can you plea

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Great! Can you please add the flag to appropriate field in the feature's chromestatus entry so that people can find the flag if needed? /Daniel On 2025-09-02 20:30, Helmut Januschka wrote: It's relanded now with a feature flag! Thanks to everyone involved, and sorry for the troubles! Helmu

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

LGTM1, conditional on the testing situation getting sorted to Dan and Domenic's satisfaction. Best, Alex On Wednesday, September 3, 2025 at 10:29:22 AM UTC+1 Noam Rosenthal wrote: > On Wed, Sep 3, 2025 at 1:59 AM Domenic Denicola > wrote: > >> >> >> On Wed, Sep 3, 2025 at 9:04 AM 'Daniel Cla

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Thanks for this, Brandon. As you know, the collateral we need to go first is much higher than when closing compatibility gaps. This explainer doesn't indicate why anyone needs the feature, show the before/after state of example code, or discuss considered alternatives. I'm inclined to support

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

On Wed, Sep 3, 2025 at 1:59 AM Domenic Denicola wrote: > > > On Wed, Sep 3, 2025 at 9:04 AM 'Daniel Clark' via blink-dev < > blink-dev@chromium.org> wrote: > >> > I believe in WPT we can't have an a.html top-frame navigate to b.html >> and check things there. I was not able to find an example in

[blink-dev] Intent to Ship: Local network access restrictions

Contact emails cth...@chromium.org Explainer https://github.com/WICG/local-network-access/blob/main/explainer.md Specification https://wicg.github.io/local-network-access Summary Chrome 141 restricts the ability for sites to make requests to the user's local network, gated behind a permissio

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

ember 2, 2025 11:04 AM > *To:* Daniel Clark > *Cc:* Chromestatus ; > blink-dev@chromium.org; vmp...@chromium.org > *Subject:* Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user > activation across same-origin navigations > > > > > > > > On Thu, Aug 28, 2025 at 9:4

RE: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

lto:blink-dev@chromium.org> mailto:blink-dev@chromium.org>> Cc: vmp...@chromium.org<mailto:vmp...@chromium.org> mailto:vmp...@chromium.org>>, mus...@chromium.org<mailto:mus...@chromium.org> mailto:mus...@chromium.org>> Subject: [EXTERNAL] [blink-dev] Intent to Ship: Stic

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

It's relanded now with a feature flag! Thanks to everyone involved, and sorry for the troubles! Helmut Januschka schrieb am Dienstag, 2. September 2025 um 11:00:20 UTC+2: > the revert was back-merged into 140, and i am working on a reland here: > http://crrev.com/c/6898599 with feature flag aro

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

ginNavigation". > -- Dan > > > *From: *blink-dev@chromium.org on behalf of > Chromestatus > *Date: *Thursday, August 28, 2025 at 1:17 PM > *To: *blink-dev@chromium.org > *Cc: *vmp...@chromium.org , mus...@chromium.org < > mus...@chromium.org> > *Subject: *[EX

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

the revert was back-merged into 140, and i am working on a reland here: http://crrev.com/c/6898599 with feature flag around the change. yoav...@chromium.org schrieb am Freitag, 29. August 2025 um 05:40:48 UTC+2: > On Thu, Aug 28, 2025 at 10:25 PM Krishna Govind wrote: > >> Thank you, any impact

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

On Thu, Aug 28, 2025 at 10:25 PM Krishna Govind wrote: > Thank you, any impact on Android Webview? Will it be safe to merge the > revert? > Yeah, it will impact Android WebViews as well. (but is safe to merge) > > Merged the revert to latest canary branch 7381 and triggered a new canary > #141

Re: [EXTERNAL] [blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

t; None This would be shipped gated by a flag, right? -- Dan From: blink-dev@chromium.org on behalf of Chromestatus Date: Thursday, August 28, 2025 at 1:17 PM To: blink-dev@chromium.org Cc: vmp...@chromium.org , mus...@chromium.org Subject: [EXTERNAL] [blink-dev] Intent to Ship: Sti

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Thank you, any impact on Android Webview? Will it be safe to merge the revert? Merged the revert to latest canary branch 7381 and triggered a new canary #141.0.7381.3, please verify once available, will approve M140 merge after canary coverage/verification. Updated the bugs: - https://g-issue

[blink-dev] Intent to Ship: Sticky user activation across same-origin navigations

Contact emails mus...@chromium.org Explainer None Specification https://github.com/whatwg/html/pull/11454 Summary This feature preserves the sticky user activation state after a page navigates to another same-origin page. The lack of user activation in the post-navigation page prevents som

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Merge request issue is at https://issues.chromium.org/issues/441770546 CL is at https://chromium-review.googlesource.com/c/chromium/src/+/6897886 On Thu, Aug 28, 2025 at 9:37 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Thu, Aug 28, 2025 at 6:21 PM 'Krishna Govind' via blink

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

On Thu, Aug 28, 2025 at 6:21 PM 'Krishna Govind' via blink-dev < blink-dev@chromium.org> wrote: > Hi Mike, > > Thank you for including Srinivas and me in this discussion. > > Since M140 was released to early stable yesterday with this feature > enabled by default and without all necessary approval

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

again, super sorry, this might be the single worst chromium day i had since my first contribution. tried to fillout everything in chromestatus entry, and request all the reviews again. a revert CL is here: https://chromium-review.googlesource.com/c/chromium/src/+/6895357 ready to review/submit. j

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

revert landet! the post mortem from my side: totally my fault, i saw the CR+1's and the Submit button, forgot about the not finished chromestatus feature entry Krishna Govind schrieb am Donnerstag, 28. August 2025 um 18:26:35 UTC+2: > +Ben Mason for awareness and visibility > > On Thu, Aug 28

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

+Ben Mason for awareness and visibility On Thu, Aug 28, 2025 at 9:21 AM Krishna Govind wrote: > Hi Mike, > > Thank you for including Srinivas and me in this discussion. > > Since M140 was released to early stable yesterday with this feature > enabled by default and without all necessary approva

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Hi Mike, Thank you for including Srinivas and me in this discussion. Since M140 was released to early stable yesterday with this feature enabled by default and without all necessary approvals, it's critical that we merge the revert to M140 and recut the M140 Stable RC for release on Tuesday, Sept

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Thanks Helmet - please don't be too hard on yourself. We've all been there. :) For now, I would recommend getting the revert landed and requesting a merge into beta. Thanks for requesting the other reviews. On 8/28/25 5:36 p.m., Helmut Januschka wrote: again, super sorry, this might be the si

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Hey Helmut, Oops. It's unfortunate that this feature is missing Privacy, Security, Enterprise, Debuggability & Testing reviews (per Chris' request back in May)... but I think more concerning is the fact that it's not guarded behind a feature flag. If we do end up breaking some sites (the risk

Re: [blink-dev] Intent to Ship: Deprecate getters of Intl Locale Info

Checking in on this again, https://chromestatus.com/metrics/feature/timeline/popularity/5232 shows increasing usage, so it would be good to decide on a path forward. Based on the use counter call sites

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Apologies! We're currently trying to decide where docs like that should live after we move them out of experimental status. In the meantime you can see the historical copy of the explainer here: https://dawn.googlesource.com/dawn/+/2819d509eff7e314e5ebce15cc3a7cb13370a505/docs/tint/extensions/chrom

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Hi all, I mistakenly landed the [CL](https://chromium-review.googlesource.com/c/chromium/src/+/6509110) in M140 before getting the intent to ship approved. My apologies for that. I'd appreciate guidance on how to proceed, given that. One way to go would be to keep the CL landed, and get your a

Re: [blink-dev] Intent to Ship: Support width and height as presentation attributes on nested elements

LGTM3 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

LGTM3 On Wed, Aug 27, 2025 at 9:52 AM Chris Harrelson wrote: > LGTM2 > > On Wed, Aug 27, 2025, 9:52 AM Daniel Bratell wrote: > >> LGTM1 >> >> Regardless of how you handle those tests for now, I assume this is just >> the first step and once the spec is complete, it will all be good. >> >> /Dani

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

The Explainer link is a 404 or has restricted access. We need the explainer to be public. /Daniel On 2025-08-25 10:56, Yoav Weiss (@Shopify) wrote: Can you request reviews for security/privacy/etc in chromestatus? On Fri, Aug 22, 2025 at 10:16 PM Chromestatus wrote: Contact e

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

LGTM2 On Wed, Aug 27, 2025, 9:52 AM Daniel Bratell wrote: > LGTM1 > > Regardless of how you handle those tests for now, I assume this is just > the first step and once the spec is complete, it will all be good. > > /Daniel > On 2025-08-25 18:45, Guido Urdaneta wrote: > > Since those tests are in

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

LGTM1 Regardless of how you handle those tests for now, I assume this is just the first step and once the spec is complete, it will all be good. /Daniel On 2025-08-25 18:45, Guido Urdaneta wrote: Since those tests are included in Interop 2025 I believe we cannot unilaterally make them tentat

Re: [blink-dev] Intent to Ship: echoCancellationMode for getUserMedia()

LGTM3 On Tue, Aug 26, 2025 at 9:01 AM 'Guido Urdaneta' via blink-dev < blink-dev@chromium.org> wrote: > On Mon, Aug 25, 2025 at 8:18 PM Alex Russell > wrote: > >> LGTM2. The extension to a property bag carries some compat risk, but >> presumably that is reduced with the property bag casting to `

Re: [blink-dev] Intent to Ship: echoCancellationMode for getUserMedia()

On Mon, Aug 25, 2025 at 8:18 PM Alex Russell wrote: > LGTM2. The extension to a property bag carries some compat risk, but > presumably that is reduced with the property bag casting to `true`, and all > of its values being some version of truthiness? > > That's correct. > Best, > > Alex > > On

Re: [blink-dev] Intent to Ship: ARIA Notify API

LGTM3 On Mon, Aug 25, 2025 at 8:08 PM Alex Russell wrote: > LGTM2; thanks for being so responsive to all the concerns raised to date. > > On Wednesday, August 20, 2025 at 11:37:40 AM UTC-7 janewman via > Chromestatus wrote: > >> The [spec PR](https://github.com/w3c/aria/pull/2577) has a couple o

Re: [blink-dev] Intent to Ship: echoCancellationMode for getUserMedia()

LGTM2. The extension to a property bag carries some compat risk, but presumably that is reduced with the property bag casting to `true`, and all of its values being some version of truthiness? Best, Alex On Monday, August 25, 2025 at 1:55:20 AM UTC-7 Yoav Weiss wrote: > LGTM1 > > On Fri, Aug

Re: [blink-dev] Intent to Ship: ARIA Notify API

LGTM2; thanks for being so responsive to all the concerns raised to date. On Wednesday, August 20, 2025 at 11:37:40 AM UTC-7 janewman via Chromestatus wrote: > The [spec PR](https://github.com/w3c/aria/pull/2577) has a couple of > LGTMs, including an approval from one of the chairs for the Aria

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

Since those tests are included in Interop 2025 I believe we cannot unilaterally make them tentative. However, it is likely that some parts of the generateKeyFrame WPTs will change after the upcoming discussion. Since we are leaving generateKeyFrame out of this launch I think the tentative status of

Re: [blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Can you request reviews for security/privacy/etc in chromestatus? On Fri, Aug 22, 2025 at 10:16 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails bajo...@chromium.org > > Explainer > https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/tint/extensions/chromium_experi

Re: [blink-dev] Intent to Ship: echoCancellationMode for getUserMedia()

LGTM1 On Fri, Aug 22, 2025 at 11:18 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails o...@google.com, gui...@google.com > > Explainer > https://github.com/guidou/mediacapture-main/blob/master/explainer-echo-cancellation-mode.md > > Specification > https://www.w3.org/TR/m

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

Can the failing tests be renamed to `.tentative` until those discussions settle? On Thu, Aug 21, 2025 at 7:42 PM Guido Urdaneta wrote: > The multi-browser failures in wpt.fyi are mainly due to their including > features that are still under discussion (SFrame and generateKeyFrame). > SFrame has

[blink-dev] Intent to Ship: WebGPU: 'primitive_index' feature

Contact emails bajo...@chromium.org Explainer https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/tint/extensions/chromium_experimental_primitive_id.md Specification https://gpuweb.github.io/gpuweb/#dom-gpufeaturename-primitive-index Summary This feature adds a new optional capability

[blink-dev] Intent to Ship: echoCancellationMode for getUserMedia()

Contact emails o...@google.com, gui...@google.com Explainer https://github.com/guidou/mediacapture-main/blob/master/explainer-echo-cancellation-mode.md Specification https://www.w3.org/TR/mediacapture-streams/#dom-echocancellationmodeenum Summary Extends echoCancellation behavior of MediaTra

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

The multi-browser failures in wpt.fyi are mainly due to their including features that are still under discussion (SFrame and generateKeyFrame). SFrame has not been shipped by any browser yet (it is not covered in the Interop 2025 effort). Safari and Firefox do have generateKeyFrame, but they are no

Re: [blink-dev] Intent to Ship: ARIA Notify API

The [spec PR](https://github.com/w3c/aria/pull/2577) has a couple of LGTMs, including an approval from one of the chairs for the Aria Working group, Valerie Young. All comments have been editorial in nature, and I am getting strong positive signals from the group when the feature is brought up i

Re: [blink-dev] Intent to Ship: Navigation API: deferred commit (precommit handlers)

LGTM3 On Wed, Aug 20, 2025 at 5:21 PM Alex Russell wrote: > LGTM2 > > On Wednesday, August 20, 2025 at 12:57:06 AM UTC-7 Yoav Weiss wrote: > >> LGTM1 >> >> This seems like a useful addition and the HTML PR work + webkit support >> makes me hopeful it will be interoperable shortly after landing.

Re: [blink-dev] Intent to Ship: Navigation API: deferred commit (precommit handlers)

LGTM2 On Wednesday, August 20, 2025 at 12:57:06 AM UTC-7 Yoav Weiss wrote: > LGTM1 > > This seems like a useful addition and the HTML PR work + webkit support > makes me hopeful it will be interoperable shortly after landing. > Please land the HTML PR before shipping, as I don't think anything i

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

LGTM3 I'd have loved getting more feedback from the broader community on this, but given the fact that the team is willing to ship breaking changes to the feature based on future feedback, that's an acceptable risk. On Wednesday, August 20, 2025 at 5:02:20 AM UTC+2 Rick Byers wrote: > On Tue,

Re: [blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

Very happy to see us approaching interoperability on this feature! Looking at https://wpt.fyi/results/webrtc-encoded-transform?label=experimental&label=master&aligned there are quite a lot of failures in all browsers. Does wpt.fyi reflect the test results we'll have after enabling this, and are th

Re: [blink-dev] Intent to Ship: Navigation API: deferred commit (precommit handlers)

LGTM1 This seems like a useful addition and the HTML PR work + webkit support makes me hopeful it will be interoperable shortly after landing. Please land the HTML PR before shipping, as I don't think anything is blocking it. On Wed, Aug 20, 2025 at 9:42 AM Noam Rosenthal wrote: > Contact email

[blink-dev] Intent to Ship: Navigation API: deferred commit (precommit handlers)

Contact emails jap...@chromium.org, dome...@chromium.org, nrosent...@chromium.org Explainer https://github.com/WICG/navigation-api#precommit-handlers Specification https://github.com/whatwg/html/pull/10919 Summary Normally, when navigateEvent.intercept() is called, the intercepted navigation

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

On Tue, Aug 19, 2025 at 7:08 AM eric trouton wrote: > Hi folks, > > Yoav, thank you for your suggestions, we reached out to the MASQUE > listserv for feedback and responded > > to TAG reviewers with more details about

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: ARIA Notify API

ll *Cc:* Jacques Newman ; blin...@chromium.org *Subject:* [EXTERNAL] Re: [blink-dev] Intent to Ship: ARIA Notify API Hi, Two questions: 1. The spec PR is still open, I'd like that to be finished before shipping. 2. The Mozilla position references an incomplete design, but thos

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

Hi folks, Yoav, thank you for your suggestions, we reached out to the MASQUE listserv for feedback and responded to TAG reviewers with more details about the utility and privacy properties. Rick, as to your question, w

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

Thank you Scott (and David), understanding the developer adoption interest is really helpful in weighing the tradeoffs around enabling this by default in Chromium! Rick On Mon, Aug 18, 2025 at 12:23 PM Scott Pierce wrote: > Integral Ad Science (IAS) is looking forward to testing PRTs to determi

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

Integral Ad Science (IAS) is looking forward to testing PRTs to determine the impact obfuscated IPs within Incognito sessions may have on ad fraud. Cheers, Scott Pierce, Head of Fraud Integral Ad Science On Monday, August 18, 2025 at 11:02:24 AM UTC-7 Rick Byers wrote: > On Fri, Aug 8, 2025 at

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

On Fri, Aug 8, 2025 at 2:39 PM 'David Turner' via blink-dev < blink-dev@chromium.org> wrote: > As a member of Google's Ad Traffic Quality team, we're excited to see the > development of PRTs and to better understand ad fraud in IP protected > traffic. > > On Wed, Aug 6, 2025 at 8:31 AM Yoav Weiss

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: ARIA Notify API

a > positive standards position would suffice I think. > > Another question: has the editorial review & approval of the ARIA WG PR > been completed? Looks like not yet from what I can see. I think that's > important as well. > > *From:* Chris Harrelson >&g

[blink-dev] Intent to Ship: Permissions Policy for Device Attributes API

Contact emails pcho...@google.com Explainer https://github.com/WICG/WebApiDevice/blob/main/DeviceAttributesPermissionsPolicyExplainer.md Specification https://github.com/WICG/WebApiDevice/blob/main/DeviceAttributesPermissionsPolicyExplainer.md Summary The new Permissions Policy enables restr

[blink-dev] Intent to Ship: WebRTC Encoded Tansform (V2)

Contact emails gui...@chromium.org, h...@chromium.org, topr...@chromium.org, alonsomo...@google.com, gui...@google.com Explainer None Specification https://github.com/w3c/webrtc-encoded-transform Summary This API allows processing of encoded media flowing through an RTCPeerConnection. Chro

Re: [blink-dev] Intent to Ship: Range syntax for style container queries and if()

LGTM3, contingent on a good answer to Anders' concern. Let's only ship when we've got high confidence. Best, Alex On Tuesday, August 12, 2025 at 12:09:35 AM UTC-7 Anders Hartvoll Ruud wrote: > On Wed, Aug 6, 2025 at 1:41 PM 'Munira Tursunova' via blink-dev < > blink-dev@chromium.org> wrote: >

[blink-dev] Intent to Ship: windowAudio for getDisplayMedia()

Contact emails k...@chromium.org, o...@chromium.org, elada...@chromium.org Explainer https://github.com/drkron/explainers/blob/main/windowAudio_Explainer.md Specification https://w3c.github.io/mediacapture-screen-share/#displaymediastreamoptions Summary Extends DisplayMediaStreamOptions for

[blink-dev] Intent to Ship: Signature-based Integrity

Contact emails mk...@chromium.org Explainer https://github.com/WICG/signature-based-sri Specification https://wicg.github.io/signature-based-sri Summary This feature provides web developers with a mechanism to verify the provenance of resources they depend upon, creating a technical foundat

Re: [blink-dev] Intent to Ship: Range syntax for style container queries and if()

On Wed, Aug 6, 2025 at 1:41 PM 'Munira Tursunova' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsmoon...@google.com > > Specification > https://drafts.csswg.org/css-conditional-5/#typedef-style-range > > Summary > > This feature enhances CSS style queries and the if() function by a

Re: [blink-dev] Intent to Ship: Range syntax for style container queries and if()

As part of reviewing this I was looking back at the Explainer and TAG review for the CSS if() function, and saw that the TAG left some good f

[blink-dev] Intent to Ship: Digital Credentials API I (presentation support)

Contact emails rby...@chromium.org, g...@chromium.org, ma...@chromium.org, ashimaar...@google.com Explainer https://github.com/w3c-fedid/digital-credentials/blob/main/explainer.md Specification https://w3c-fedid.github.io/digital-credentials Summary Websites can and do get credentials from

Re: [blink-dev] Intent to Ship: Update hidden=until-found and details ancestor revealing algorithm

LGTM3 On Friday, August 8, 2025 at 8:55:56 AM UTC-7 Chris Harrelson wrote: > LGTM2 > > On Fri, Aug 8, 2025 at 8:33 AM Mike Taylor wrote: > >> LGTM1 >> On 8/7/25 4:31 p.m., Joey Arhar wrote: >> >> Contact emails jar...@chromium.org >> >> Explainer None >> >> Specification https://github.com/whatw

Re: [blink-dev] Intent to Ship: CSS :lang pseudo class level 4

Hi, The CL has been merged and this feature is now available behind the *CSSLangExtendedRanges* runtime flag. Best, Felipe On Monday, 7 July 2025 at 14:06:41 UTC+9 felip...@gmail.com wrote: > Hi, > > After coordinating with my colleague Roger Zanoni, I will continue the > development and ship

Re: [blink-dev] Intent to Ship: Probabilistic Reveal Tokens

As a member of Google's Ad Traffic Quality team, we're excited to see the development of PRTs and to better understand ad fraud in IP protected traffic. On Wed, Aug 6, 2025 at 8:31 AM Yoav Weiss (@Shopify) wrote: > Presenting this to various IETF groups in November sounds like a good > idea, but

Re: [blink-dev] Intent to Ship: Update hidden=until-found and details ancestor revealing algorithm

LGTM2 On Fri, Aug 8, 2025 at 8:33 AM Mike Taylor wrote: > LGTM1 > On 8/7/25 4:31 p.m., Joey Arhar wrote: > > Contact emails jar...@chromium.org > > Explainer None > > Specification https://github.com/whatwg/html/pull/11457 > > Summary > > The spec recently had some small changes to the revealing

Re: [blink-dev] Intent to Ship: Update hidden=until-found and details ancestor revealing algorithm

LGTM1 On 8/7/25 4:31 p.m., Joey Arhar wrote: Contact emails jar...@chromium.org Explainer None Specification https://github.com/whatwg/html/pull/11457 Summary The spec recently had some small changes to the revealing algorithms for hidden=until-found

[blink-dev] Intent to Ship: Update hidden=until-found and details ancestor revealing algorithm

Contact emailsjar...@chromium.org ExplainerNone Specificationhttps://github.com/whatwg/html/pull/11457 Summary The spec recently had some small changes to the revealing algorithms for hidden=until-found and details elements in order to prevent the browser from getting stuck in an infinite loop:

Re: [blink-dev] Intent to Ship: FedCM: Alternative Fields in Account Selection

Thanks everyone for the LGTMs! And thanks specifically to Mike for pointing that out, I have updated the chromestatus entry to indicate that the TAG is satisfied Christian On Wed, Aug 6, 2025 at 3:47 PM Mike Taylor wrote: > LGTM3 (and noting that the TAG review was closed as satisfied). > On 8

  1   2   3   4   5   6   7   8   9   10   >