Re: [blink-dev] Intent to Ship: CSS sibling-index() and sibling-count()

On Tue, May 13, 2025 at 7:43 AM Domenic Denicola wrote: > I'm very slightly worried about the cases which we seem to accept, but the > latest on the CSSWG thread suggests we should disallow. Namely, @container > and @page. How sure are you that changing those to be invalid in the > future, to fol

Re: [blink-dev] Intent to Ship: CSS sibling-index() and sibling-count()

I'm very slightly worried about the cases which we seem to accept, but the latest on the CSSWG thread suggests we should disallow. Namely, @container and @page. How sure are you that changing those to be invalid in the future, to follow the latest CSSWG decisions, will not cause compat problems

Re: [blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

Thank you! I added the relevant information on ChromeStatus. *--* *Cheers,* *Michał* On Tue, May 13, 2025 at 7:39 AM Domenic Denicola wrote: > LGTM1, but please update the following bits on ChromeStatus: > >- Estimated milestones. This is important for ensuring developers have >an accu

Re: [blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

LGTM1, but please update the following bits on ChromeStatus: - Estimated milestones. This is important for ensuring developers have an accurate picture of when changes like this are rolling out. Especially if this will be a gradual rollout of some sort, or has previously been tested in

Re: [blink-dev] PSA: HTMLFencedFrameElement.canLoadOpaqueURL() to be removed

On 5/9/25 6:21 PM, Shivani Sharma wrote: On Fri, May 9, 2025 at 4:25 PM Mike Taylor wrote: On 5/8/25 9:56 AM, Xiaochen Zhou wrote: The functionality of canLoadOpaqueURL() was replaced with navigator.canLoadAdAuctionFencedFrame()

Re: [blink-dev] Intent to Ship: Pass 'Sec-Purpose: prefetch' header with

Yes, thanks for the reminder. This is my first Intent to Ship so will note this for future ones! On Monday, May 12, 2025 at 2:32:23 PM UTC-7 mike...@chromium.org wrote: > Before continuing the review, could you please request all the privacy, > security, enterprise, etc bits in the chromestatu

Re: [blink-dev] Intent to Ship: CSS sibling-index() and sibling-count()

LGTM1 On 5/9/25 9:47 AM, Rune Lillesveen wrote: Contact emails futh...@chromium.org, se...@chromium.org Explainer https://github.com/w3c/csswg-drafts/blob/main/css-values-5/tree-counting-explainer.md Specification https://drafts.csswg.

Re: [blink-dev] Intent to Extend Experiment: Playout Statistics API for WebAudio

Thanks for the updates on progress. LGTM to extend from M137 to M139 inclusive. On 5/9/25 10:27 AM, 'Fredrik Hernqvist' via blink-dev wrote: Contact emails fhernqv...@google.com, o...@google.com, hongc...@google.com, agpa...@google.com, gui...@google.com Explainer https:

Re: [blink-dev] Intent to Ship: Pass 'Sec-Purpose: prefetch' header with

Before continuing the review, could you please request all the privacy, security, enterprise, etc bits in the chromestatus entry? On 5/12/25 2:32 PM, 'Steven Wei' via blink-dev wrote: domenic@ found the place in HTML spec that already mentioned this header for prefetch: Fetch Standard

Re: [blink-dev] Ready for Developer Testing: Modulepreload Referrer Header Fix

I suspect this is supposed to be an I2S (per https://chromium-review.googlesource.com/c/chromium/src/+/6509110/comments/da10e968_f515270f), but if "Ready for Developer Testing" is the correct stage - a feature flag for devs to flip and test would be useful. Could you clarify? Thanks On 5/8/25

[blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

Out of curiosity, which platforms will this not be supported on, and why? Sorry, I put the wrong value there -- it will be supported on all platforms. Given that Firefox has implemented this (Nightly-only), as well as Safari (not landed yet?), do we know why https://github.com/whatwg/html/p

Re: [blink-dev] Intent to Ship: Pass 'Sec-Purpose: prefetch' header with

domenic@ found the place in HTML spec that already mentioned this header for prefetch: Fetch Standard

Re: [blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

Given that Firefox has implemented this (Nightly-only ), as well as Safari (not landed yet? ), do we know why https://github.com/whatwg/html/pull/6362 hasn't been merged yet? On 5/12/25 11:23 AM

[blink-dev] Re: Intent to Ship: Escape "<" and ">" in attributes on serialization

Out of curiosity, which platforms will this not be supported on, and why? Thanks, Alison On Friday, May 9, 2025 at 2:18:27 AM UTC-7 Chromestatus wrote: > Contact emails secur...@google.com > > Explainer https://github.com/whatwg/html/issues/6235 > > Specification https://github.com/whatwg/html

Re: [blink-dev] Intent to Ship: Fire error event instead of throwing for CSP blocked worker

Thanks for taking another look at this. Will wait for a month to see whether we could get a list of URLs that hit the scenario to check them. The behavior (return a worker object and later firing an error event on it) already happen when loading the script failed. That is actually what CSP tryi

Re: [blink-dev] Intent to Ship: Pass 'Sec-Purpose: prefetch' header with

Thanks! Added an issue to whatwg/html repo: Can we include what header(s) get sent with link type prefetch? · Issue #11294 · whatwg/html Also, I don't think Safari supports . Also, started vendor position requests: Mozilla: Send Sec-Purpose header f