Re: [blink-dev] Intent to Ship: Link rel=payment to support push payments

Thanks Jeffrey for the input on the second question! > What happens if the page contains multiple payment client schemes (to cover more ground) and the buyer has more than one of these clients installed? Will Chromium's prompt let users choose their preferred option, as step 10

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

Just to clarify - currently both Chromium, WebKit and (most?) deployments in the wild match one behavior and the spec calls for another? On Friday, March 28, 2025 at 6:20:28 PM UTC+1 philipp...@googlemail.com wrote: > Am Fr., 28. März 2025 um 08:31 Uhr schrieb Harald Alvestrand < > h...@google.

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

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 > > dizha...@chromium.org > > Explainer > > None > > Specification > > https://www.w3.org/TR/css-display-4 > > Summary > > The reading-flow

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

My concerns about this are summarised here , and subsequent comments on the thread. I think this is different to the usual risks around IDs. Usually IDs are referenced directly by their full name, in HTML like , in links

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

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 > small addition to an existing spec and it has consensus across browsers, it > is possi

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

I remain unconvinced that the benefits of this feature (the ability to "magically" get transitions across documents) outweigh its ecosystem costs (footgun around the use of IDs, partial application of transitions in the cross-document case). At the very least, it seems like the name of the feat

Re: [blink-dev] Intent to Ship: Rename `string` attr() type to `raw-string`

Thank you for checking. LGTM1 On Thu, Mar 20, 2025 at 10:09 AM 'Munira Tursunova' via blink-dev < blink-dev@chromium.org> wrote: > Checked the websites with potential breakages, don't observe any > breakages. > The only website with visual differences is > https://css3test.com/#css-values-5, but

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

Contact emailsbing...@chromium.org, miketa...@chromium.org, la...@chromium.org Explainer https://github.com/explainers-by-googlers/HSTS-Tracking-Prevention Specification Draft-bingler-hsts-tracking-prevention

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

On Wednesday, April 2, 2025 at 12:04:23 PM UTC-4 Dale Curtis wrote: 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 e

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

Sorry for the delay, for some reason Alex's message didn't show up in my inbox! *Alex*: Up to 100% of Storage Access API (SAA) usage could be affected, if we assume that *every *usage of SAA later involves a cross-origin, same-site network request that is required to be credentialed. However,

Re: [blink-dev] Intent to Ship: Rename `string` attr() type to `raw-string`

I see there are 3 LGTMs now, and I'm not going to block, but I want to be extremely clear that this is not precedent and that folks who have asked for this change should take note that I might block future changes of this sort if we see this kind of thing become a habit from the CSS WG. Best,

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Use DOMPointInit for getCharNumAtPosition, isPointInFill, isPointInStroke

LGTM1 On Wednesday, March 26, 2025 at 10:55:35 AM UTC-4 vinay...@microsoft.com wrote: > Yes, createSVGPoint() will still work. > We have a WPT as well to ensure it. > > https://wpt.fyi/results/svg/types/scripted/SVGGeometryElement.isPointInStroke-02.svg > > Thanks, > Vinay >

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

We can discuss lifetimes of other stats objects, but that seems largely tangential to this I2S thread. Good to hear you are supportive of delating the outbound RTP stats objects until "stable" which is half of this I2S. The other half being delaying inbound. But I think browser alignment here i

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Update HTTP request headers, body, and referrer policy on CORS redirect

The change is in 135, sorry for the delay. Happy to make any changes. Thanks, Viktoria From: Vladimir Levin Sent: Tuesday, March 18, 2025 7:57 PM To: blink-dev Cc: Viktoria Zlatinova Subject: [EXTERNAL] Re: [blink-dev] Intent to Ship: Update HTTP request header

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

TAG review issue open: https://github.com/w3ctag/design-reviews/issues/1078 Victor On Tuesday, April 1, 2025 at 10:42:44 PM UTC-4 Vladimir Levin wrote: > Can you file the various review gates as well? > [image: Screenshot 2025-04-01 at 10.42.12 PM.png] > > > TAG reviewTo be filed > > > Is thi

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 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] 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 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: [EXTERNAL] Re: [blink-dev] Intent to Remove: SwiftShader Fallback

Thanks for chiming in Matt. Is the scenario you described Windows-only (in which case we should be good with WARP), or also Linux? Rick On Mon, Mar 24, 2025 at 1:22 PM Matt George wrote: > Very happy to hear about exploring the use of WARP on windows. > > Just wanted to chime in that from the E

Re: [blink-dev] Intent to Prototype: Noising canvas readbacks in Incognito

Will it allow detection of incognito mode, though? Hopefully not... ☆*PhistucK* On Mon, Mar 17, 2025 at 11:15 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails t...@chromium.org, antoniosart...@chromium.org, > johny...@google.com, riz...@google.com > > Explainer > http