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

LGTM3 On Wed, Apr 2, 2025 at 8:21 AM Alex Russell wrote: > LGTM2, with some disappointment on two fronts: > > - why do we keep doing this these JSON-ish declarative forms without > adding any sort of DOM? It's maddening. > - we're backing into many things that effectively map to headers. Why n

[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

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

Contact emails ta...@google.com, riz...@google.com Explainer https://github.com/explainers-by-googlers/limiting-local-fonts-access?tab=readme-ov-file Specification None Summary Limits the fonts websites can use to only the default system fonts installed by the operating system. The unique s

[blink-dev] Web-Facing Change PSA: Navigations can now be captured into an installed PWA

Contact emails dibya...@chromium.org pwa-...@chromium.org Design Doc https://bit.ly/pwa-navigation-capturing Developer Documentation https://bit.ly/pwa-navigation-management https://youtu.be/OFH9TfrqZCY Chrome Status Entry https://chrom

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, I've addressed the following issues and re-requested a review for this. ✓ Worked with pade...@mozilla.com and others from the Audio WG in finalizing the API shape for on-device speech recognition. ✓ Expanded WPT coverage for on-device functionality ✓ Dropped the "webkit" prefix from the W

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

During the 1% stable experiment period, I don't think those sites adopted Avail-Language. For now, we can keep monitoring any significant changes over the translation metrics and feature related metrics. 2.6% embedded iframes changing means they change content with different Accept-Language, it inc

[blink-dev] Intent to Prototype: Web App Manifest: "update_token" and update eligibility

Contact emailsfin...@google.com, dibya...@google.com Explainer https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md SpecificationNone Summary Introduce an `update_token` field and update eligibility algorithm to the manifest spec. This makes the update process

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

Thanks all! On Tue, Apr 1, 2025 at 10:18 PM Vladimir Levin wrote: > LGTM3 > > On Tuesday, April 1, 2025 at 3:51:41 PM UTC-4 beham...@google.com wrote: > >> Can I get an update on this? >> >> Thanks, >> --Benjamin "Russ" Hamilton >> >> On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor >> wrote: >> >>

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

LGTM2, with some disappointment on two fronts: - why do we keep doing this these JSON-ish declarative forms without adding any sort of DOM? It's maddening. - we're backing into many things that effectively map to headers. Why not just add a "headers" sub-field to the structure and allow a full

Re: [blink-dev] Intent to Ship: Add support for video frame orientation metadata to WebCodecs

On Wed, Apr 2, 2025 at 8:37 AM Vladimir Levin wrote: > > > On Wednesday, April 2, 2025 at 12:05:53 AM UTC-4 Dale Curtis wrote: > > On Tue, Apr 1, 2025 at 7:16 PM Vladimir Levin wrote: > > Some cameras and media will immediately begin exposing orientation > information. In uncommon cases this ori

[blink-dev] Re: Intent to Ship: WebGPU: copyBufferToBuffer overload

LGTM1, but would be good to see the other review sections started. On Wednesday, April 2, 2025 at 1:15:47 AM UTC-7 fbea...@google.com wrote: > Contact emails > > fbeauf...@google.com > > Explainer > > To simplify the copy of entire buffers, a new overload has been added to > the GPUCommandEncode

Re: [blink-dev] Re: Intent to Ship: CapturedSurfaceResolution

LGTM3 /Daniel On 2025-04-02 17:11, Alex Russell wrote: LGTM2 On Tuesday, April 1, 2025 at 11:55:16 PM UTC-7 Guido Urdaneta wrote: On Wed, Apr 2, 2025 at 4:33 AM Vladimir Levin wrote: LGTM1 Interoperability risk is relatively low. The main risk

Re: [blink-dev] Intent to Ship: Add support for video frame orientation metadata to WebCodecs

On Wednesday, April 2, 2025 at 12:05:53 AM UTC-4 Dale Curtis wrote: On Tue, Apr 1, 2025 at 7:16 PM Vladimir Levin wrote: Some cameras and media will immediately begin exposing orientation information. In uncommon cases this orientation may change. If orientation changes during encoding throu

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

Hi, Vladimir, Thanks for the reminder. I requested those review gates. For the TAG review, I will publish soon and link the issue here once it is published. Jeffrey, Thanks for raising this concern. We understand that some popular multilingual sites

Re: [blink-dev] Intent to Ship: CSS reading-flow, reading-order properties

LGTM3 On Wednesday, April 2, 2025 at 8:28:54 AM UTC-7 sligh...@chromium.org wrote: > LGTM2 > > On Wednesday, April 2, 2025 at 6:57:22 AM UTC-7 Daniel Bratell wrote: > >> LGTM1 >> >> /Daniel >> On 2025-04-01 00:11, Di Zhang wrote: >> >> Contact emails >> >> dizh...@chromium.org >> >> Explainer >

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

LGTM3 On Wednesday, April 2, 2025 at 11:21:08 AM UTC-4 Alex Russell wrote: > LGTM2, with some disappointment on two fronts: > > - why do we keep doing this these JSON-ish declarative forms without > adding any sort of DOM? It's maddening. > - we're backing into many things that effectively map

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: [blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

LGTM3 On Wed, Apr 2, 2025 at 8:05 AM Vladimir Levin wrote: > LGTM2. > > Thanks for clarifying. > > On Wednesday, April 2, 2025 at 10:58:54 AM UTC-4 lbr...@google.com wrote: > >> > There's a bit of an overloaded terminology that confuses me: when you >> refer to a cross-origin subframe, are we ta

[blink-dev] Re: Intent to Ship: CapturedSurfaceResolution

LGTM2 On Tuesday, April 1, 2025 at 11:55:16 PM UTC-7 Guido Urdaneta wrote: > On Wed, Apr 2, 2025 at 4:33 AM Vladimir Levin wrote: > >> LGTM1 >> >> >> Interoperability risk is relatively low. The main risk is that other >> browsers do not implement the feature. However, since the feature is a

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

> There's a bit of an overloaded terminology that confuses me: when you refer to a cross-origin subframe, are we talking about a cross-origin fenced frame or an iframe? My recollection is that in a fenced frame case, one cannot use postMessage to communicate with its embedder. Having this data

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

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 promise of FedCM always was that it could be a sin

Re: [blink-dev] Intent to Ship: CSS reading-flow, reading-order properties

LGTM1 /Daniel On 2025-04-01 00:11, Di Zhang wrote: Contact emails dizha...@chromium.org Explainer None Specification https://www.w3.org/TR/css-display-4 Summary The reading-flow CSS property controls the order in which elements in a flex, grid or

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

LGTM3 /Daniel On 2025-04-02 15:05, Mike Taylor wrote: 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() synt

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: Rename `string` attr() type to `raw-string`

To close the loop: the PR to update MDN got approved just now and should be deployed later today. On Monday, March 24, 2025 at 7:15:35 PM UTC+1 Alex Russell wrote: > I see there are 3 LGTMs now, and I'm not going to block, but I want to be > extremel

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

Contact emails fbeauf...@google.com Explainer Some developers using WebGPU for video effects pipelines have proposed allowing a compatible GPUTextureView (2D, single subresource) to be used in place of a GPUExternalTexture binding. This would simplify their shader logic, which currently needs to

[blink-dev] Intent to Ship: WebGPU: copyBufferToBuffer overload

Contact emails fbeauf...@google.com Explainer To simplify the copy of entire buffers, a new overload has been added to the GPUCommandEncoder copyBufferToBuffer() method, allowing developers to omit offsets and size parameters. https://github.com/gpuweb/gpuweb/pull/5098 Specification https://