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

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/binary.html > (yes, it's extremely simple) > I updated the li

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

The WPT tests failing is mostly because Safari still using the old specification for getComposedRanges() syntax. This change was resolved in September 2024: https://github.com/w3c/selection-api/pull/331 I have opened an issue with MDN to update the site: https://github.com/mdn/content/issues/38

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

LGTM2 On Wed, Mar 26, 2025 at 8:22 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > 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/resul

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

OK - makes sense to me. LGTM1 On 3/26/25 10:29 AM, Liam Brady wrote: > Why does that override the need to send the header? The intention is to have the cross-origin subframe's document explicitly opt in to the automatic beacon transaction. This is done in order to safeguard the click event i

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

LGTM3 /Daniel On 2025-03-26 16:24, Chris Harrelson wrote: LGTM2 On Wed, Mar 26, 2025 at 8:22 AM Yoav Weiss (@Shopify) wrote: 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

[blink-dev] Intent to Prototype: Expose Initiator info in resource timing

Contact emails guohuid...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ResourceTimingInitiatorInfo/explainer.md Specification None Summary In performanceResourceTiming, expose the "initiator info". "Initiator info" is infor

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

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

It's unconvincing re: deprecation risk that Apple has decided in the short run that they don't want to unship to deliver a better feature (without the benefits of developer-oriented quality protections that our process provides). We should always be trying to answer the question "*does this sol

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

LGTM3 On Tue, Mar 25, 2025 at 6:48 AM Mike Taylor wrote: > > On 3/24/25 10:24 PM, Domenic Denicola wrote: > > > > On Mon, Mar 24, 2025 at 4:37 PM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Mon, Mar 24, 2025 at 6:45 AM Domenic Denicola >> wrote: >> >>> Great to hear!

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

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 performance and ergonomics optimization for developers > only, right? > > LGTM1 >

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

> Why does that override the need to send the header? The intention is to have the cross-origin subframe's document explicitly opt in to the automatic beacon transaction. This is done in order to safeguard the click event itself, not just the data that would be attached to the beacon. If that cros

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

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 been updated yet... > [1]: https://github.com/w3c/csswg-drafts/issues/11500 Tab landed spec edits for that: https://gi

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

Sounds fine - a performance and ergonomics optimization for developers only, right? LGTM1 On Tue, Mar 25, 2025 at 12:01 PM 'Russ Hamilton' via blink-dev < blink-dev@chromium.org> wrote: > Explainer > > > https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md#devic

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

LGTM1 On Tue, Mar 25, 2025 at 1:57 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails gabrielbr...@microsoft.com, stev...@microsoft.com > > Explainer > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AudioContextInterruptedState/explainer.md > > Specification >

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

LGTM3 On Wednesday, March 26, 2025 at 8:18:37 AM UTC-7 Chris Harrelson wrote: > LGTM2 > > On Wed, Mar 26, 2025 at 8:17 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> LGTM1 >> >> On Wednesday, March 19, 2025 at 6:18:09 PM UTC-4 junh...@google.com >> wrote: >> >> Thanks Jeffrey f

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

Thanks, Chris. We discussed briefly at today's API OWNERs, and Vlad and I are in the same boat (I think?), which is that we're glad that you were able to confirm our understanding of the situation, but the risk continues to look high in that light. There's generally a menu of options in these

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

LGTM1 On Wednesday, March 19, 2025 at 6:18:09 PM UTC-4 junh...@google.com wrote: 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 Chr

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

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 From: TAMURA, Kent Sent: Wednesday, March 26, 2025 05:20 AM To: Vinay Singh ; blink-dev@ch

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

LGTM3 On 3/24/25 10:28 PM, Domenic Denicola wrote: LGTM2. I don't believe a gradual Finch rollout is necessary. (Nor do I think it's a good idea; it would lead to non-reproducible heisenbugs for web developers where they see different results in different browser sessions.) But, we should

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

Ah, I looked in the wrong "binary" rendering of the spec. This is the correct link: https://webassembly.github.io/branch-hinting/metadata/code/binary.html (yes, it's extremely simple) I updated the link in the feature. Sorry for the confusion! On Wed, Mar 26, 2025 at 10:31 AM Emanuel Ziegler wrot

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

See answers below. Thanks! On Wed, Mar 26, 2025 at 2:26 AM Domenic Denicola wrote: > > > 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 Gr