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

I've summarised the issues with this proposal in the TAG thread . On Tue, 25 Mar 2025 at 10:44, Noam Rosenthal wrote: > >> >> *Until this feature (correct me if I'm wrong), adding a unique ID to an >> element was safe

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

On Tue, 25 Mar 2025 at 10:31, Yoav Weiss wrote: > On Tuesday, March 25, 2025 at 5:12:17 AM UTC-4 Jake Archibald wrote: > > This issue wouldn't happen if any of the following was done instead: > > >- Each element was assigned a unique view-transition-name ident >- view-transition-name: mat

[blink-dev] Intent to Prototype: Column wrapping for multicol

Contact emailsmsten...@chromium.org Explainerhttps://github.com/mstensho/column-wrap Specificationhttps://drafts.csswg.org/css-multicol-2 Summary Add support for the `column-wrap` and `column-height` CSS properties, from multicol Level 2. https://drafts.csswg.org/css-multicol-2/#cwr https://dra

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

Hi all, We are preparing to ship the WebAssembly Branch Hints proposal in M136 which has been voted to phase 4 in the Wasm Community Group last July. Chrome is now catching up with shipping it after requests from partners. The feature is already implemented in Firefox. The proposal was championed

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

On Tue, Mar 25, 2025 at 12:10 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails dalecur...@chromium.org > > Explainer None > > Specification https://www.w3.org/TR/webcodecs > > Summary > > Introduces "rotation: int" and "flip: bool" values to various video > related interf

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

On Tuesday, March 25, 2025 at 5:12:17 AM UTC-4 Jake Archibald wrote: Let me try and explain the breaking case again. I'll describe it in terms of a React component for brevity, but the same issue exists with regular DOM. Here's a basic list of items, with a button that randomises the order of

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

Contact emails dalecur...@chromium.org Explainer None Specification https://www.w3.org/TR/webcodecs Summary Introduces "rotation: int" and "flip: bool" values to various video related interfaces in WebCodecs so that developers can work with frame sources that have orientation (Eg, Android

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

Thanks for the feedback! I've updated the status accordingly, setting the feedback from Mozilla and web developers to Positive (after all it was championed by a web developer). I'm not sure if Mozilla already shipped the feature, but at least it's fully implemented since M127

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

Explainer https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md#device-orchestrated-multi-seller-auctions https://github.com/WICG/turtledove/pull/1403 Specification https://wicg.github.io/turtledove/#getInterestGroupAdAuctionData https://github.com/WICG/turtle

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

Contact emails dizha...@chromium.org Explainer None Specification https://w3c.github.io/selection-api/#dom-selection-getcomposedranges Summary This feature ships two new API methods for the Selection API: * Selection.direction which returns the selection's direction as either "none", "forward

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

On Wed, Mar 26, 2025 at 2:59 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails vinaysi...@microsoft.com > > Explainer None > > Specification https://svgwg.org/svg2-draft > > Summary > > This change brings Chromium code in line with the latest W3C spec for > SVGGeometryElem

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

On Tue, Mar 25, 2025 at 9:49 PM Emanuel Ziegler wrote: > Hi all, > > We are preparing to ship the WebAssembly Branch Hints proposal in M136 > which has been voted to phase 4 in the Wasm Community Group last July. > Chrome is now catching up with shipping it after requests from partners. > The fea

[blink-dev] Ready for Developer Testing: CSS find-in-page highlight pseudos

Contact emails schen...@chromium.org, dazab...@igalia.com Explainer https://github.com/Igalia/explainers/blob/main/css/find-in-page/README.md Specification https://drafts.csswg.org/css-pseudo-4/#selectordef-search-text Design docs https://github.com/Igalia/explainers/blob/main/css/find-in-pa

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

> 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 should be a much more readable version of w

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

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 the dom (for a custom attribute). > Doing these modification

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

On Tue, Mar 25, 2025 at 3:13 PM Dale Curtis wrote: > On Tue, Mar 25, 2025 at 9:44 AM Stephen Chenney > wrote: > >> >> >> On Tue, Mar 25, 2025 at 12:10 PM Chromestatus < >> ad...@cr-status.appspotmail.com> wrote: >> >>> Contact emails dalecur...@chromium.org >>> >>> Explainer None >>> >>> Specifi

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

Contact emails gabrielbr...@microsoft.com, stev...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AudioContextInterruptedState/explainer.md Specification https://webaudio.github.io/web-audio-api/#dom-audiocontextstate-interrupted Summary The current Web A

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

Contact emails vinaysi...@microsoft.com Explainer None Specification https://svgwg.org/svg2-draft Summary This change brings Chromium code in line with the latest W3C spec for SVGGeometryElement and SVGPathElement in terms of usage of DOMPointInit over SVGPoint for getCharNumAtPosition, is

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

On Tue, Mar 25, 2025 at 9:44 AM Stephen Chenney wrote: > > > On Tue, Mar 25, 2025 at 12:10 PM Chromestatus < > ad...@cr-status.appspotmail.com> wrote: > >> Contact emails dalecur...@chromium.org >> >> Explainer None >> >> Specification https://www.w3.org/TR/webcodecs >> >> Summary >> >> Introduce

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

I think you have a stronger interop story than the fields would indicate ... On Tue, Mar 25, 2025 at 8:49 AM Emanuel Ziegler wrote: > Hi all, > > We are preparing to ship the WebAssembly Branch Hints proposal in M136 > which has been voted to phase 4 in the Wasm Community Group last July. > Chro

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

On 3/24/25 10:24 PM, Domenic Denicola wrote: On Mon, Mar 24, 2025 at 4:37 PM Yoav Weiss (@Shopify) wrote: On Mon, Mar 24, 2025 at 6:45 AM Domenic Denicola wrote: Great to hear! I see you've already updated the spec PR. My instinct is that we should give

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

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 the dom (for a custom attribute). Doing these modification is not far from just giving unique names to view-transition-name,

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

On Tue, Mar 25, 2025 at 1:52 PM Mike Taylor wrote: > 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 ot

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

Looking at the WPT results, there are a lot of Safari failures despite them having already shipped this. https://wpt.fyi/results/selection/shadow-dom/tentative?label=experimental&label=master&aligned Do you have an understanding of what those gaps are, and whether there's a path towards resolving