Re: [blink-dev] Intent to Ship: Crash Reporting API: is_top_level & visibility_state

I filed a question on the specification repository which I'd like to see discussed before we ship this: https://github.com/WICG/crash-reporting/issues/26 On Wed, May 14, 2025 at 6:21 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails d...@chromium.org > > Explainer https:/

Re: [blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

On Wed, May 14, 2025 at 5:10 AM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails hjanusc...@gmail.com > > Explainer None > > Specification > https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload:script-fetch-options > > Summary > > Fixes modulepreload to

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

The experiment was also enabled on 50% of Beta. Wouldn't that catch potential Enterprise breakages? On Tuesday, May 13, 2025 at 8:25:44 PM UTC+2 Alex Russell wrote: > LGTM3 with the caveat that we likely have risks to enterprise apps that > wouldn't have been visible from the 10% Finch experiem

[blink-dev] Re: Intent to Ship: Update QuotaExceededError to a DOMException derived interface

On Wed, May 14, 2025 at 3:21 AM Alex Russell wrote: > Thanks for flipping the bits, Ayu. > > Domenic: it seems like this is part of a longer-running set of changes > we've had going in DOM-land regarding moving away from subclasses of Error > types, and IIRC this is a motivating factor in the TAG

[blink-dev] Intent to Ship: Crash Reporting API: is_top_level & visibility_state

Contact emails d...@chromium.org Explainer https://github.com/WICG/crash-reporting/issues/20 https://github.com/WICG/crash-reporting/issues/14 https://github.com/WICG/crash-reporting/pull/23 Specification https://github.com/WICG/crash-reporting/pull/23 Design docs https://github.com/WICG/cra

[blink-dev] Intent to Prototype: The ident() function

Contact emails andr...@chromium.org Explainer None Specification https://drafts.csswg.org/css-values-5/#ident Summary The ident() function may be used to construct CSS identifiers dynamically, eg the concatenation of a string part and an integer part. Blink component Blink>CSS Motivati

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

sorry for the confusion, it was my first time using https://www.chromestatus.com/features lets close this one, i just re-sent the feature with i2s mike...@chromium.org schrieb am Montag, 12. Mai 2025 um 22:59:25 UTC+2: > I suspect this is supposed to be an I2S (per > https://chromium-review.go

[blink-dev] Intent to Ship: Modulepreload Referrer Header Fix

Contact emails hjanusc...@gmail.com Explainer None Specification https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload:script-fetch-options Summary Fixes modulepreload to properly send referrer headers by using ClientReferrerString() instead of NoReferrer(). This aligns

Re: [blink-dev] Intent to Ship: Deprecate asynchronous range removal for Media Source Extensions

LGTM1 to change the behaviour. /Daniel On 2025-05-13 20:30, Dale Curtis wrote: The plan is to land the change right away given the low usage and long shipped state on other UAs. - dale On Tue, May 13, 2025 at 10:57 AM Daniel Bratell wrote: Do you just want to deprecate it (i.e. add s

Re: [blink-dev] Intent to Ship: Deprecate asynchronous range removal for Media Source Extensions

The plan is to land the change right away given the low usage and long shipped state on other UAs. - dale On Tue, May 13, 2025 at 10:57 AM Daniel Bratell wrote: > Do you just want to deprecate it (i.e. add some warning when used) or do > you want to do the change right away? Doing the change ri

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

LGTM3 with the caveat that we likely have risks to enterprise apps that wouldn't have been visible from the 10% Finch experiement, and so we should do this on-by-default in Beta for most of a cycle, and make sure that we have a kill-switch in place in case of potential enterprise breakage in St

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

LGTM2 On Tuesday, May 13, 2025 at 11:21:54 AM UTC-7 dan...@microsoft.com wrote: > LGTM1 > > On Monday, May 12, 2025 at 3:00:13 PM UTC-7 stev...@microsoft.com wrote: > >> Yes, thanks for the reminder. This is my first Intent to Ship so will >> note this for future ones! >> >> On Monday, May 12,

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

LGTM1 On Monday, May 12, 2025 at 3:00:13 PM UTC-7 stev...@microsoft.com wrote: > 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, coul

[blink-dev] Re: Intent to Ship: Update QuotaExceededError to a DOMException derived interface

Thanks for flipping the bits, Ayu. Domenic: it seems like this is part of a longer-running set of changes we've had going in DOM-land regarding moving away from subclasses of Error types, and IIRC this is a motivating factor in the TAG's Design Principles guidance on error types

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Just to circle back on this since the thread was not updated: https://chromium-review.googlesource.com/c/chromium/src/+/6406078 solved the problem and enabled the tests, and https://chromium-review.googlesource.com/c/chromium/src/+/6448729 re-enabled the feature to launch. Per https://chromiumdash.

Re: [blink-dev] Intent to Ship: Deprecate asynchronous range removal for Media Source Extensions

Do you just want to deprecate it (i.e. add some warning when used) or do you want to do the change right away? Doing the change right away seems reasonable. /Daniel On 2025-05-13 18:44, Chromestatus wrote: Contact emails dalecur...@chromium.org Explainer None S

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

Thanks! I updated the "Interoperability and Compatibility Risks" already on ChromeStatus. *--* *Cheers,* *Michał* On Tue, May 13, 2025 at 7:47 PM Daniel Bratell wrote: > LGTM2 > > You left the Compatibility field empty which I don't think is accurate. > There is always a risk that sites depend

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

LGTM2 You left the Compatibility field empty which I don't think is accurate. There is always a risk that sites depend on the exact output of a function so please keep an eye open for any reported issues. /Daniel On 2025-05-13 07:55, 'Michał Bentkowski' via blink-dev wrote: Thank you! I ad

[blink-dev] Intent to Ship: Deprecate asynchronous range removal for Media Source Extensions

Contact emails dalecur...@chromium.org Explainer None Specification https://w3c.github.io/media-source Summary The Media Source standard long ago changed to disallow ambiguously defined behavior involving asynchronous range removals: * SourceBuffer.abort() no longer aborts SourceBuffer.rem

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

On Tue, May 13, 2025 at 8:34 AM Rune Lillesveen wrote: > 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