[blink-dev] Re: Intent to Extend Experiment: ServiceWorkerStaticRouterTimingInfo

LGTM to extend to 139. I see a draft spec, completed TAG review, signals requests sent in 2024-05, and fairly comprehensive WPTs. On Wed, May 7, 2025 at 5:45 PM Keita Suzuki wrote: > Contact emailssuzukike...@chromium.org, yyanagis...@chromium.org > > Explainer > https://github.com/WICG/service-

[blink-dev] Intent to Prototype: CSS Color for Color Input Value

Contact emails lwar...@igalia.com Explainer None Specification https://html.spec.whatwg.org/multipage/input.html#update-a-color-well-control-color Summary The HTML color input historically only supported 6 digit hex values for the value attribute. This feature changes that to support the mu

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent color for accent-color property.

+1 to Joey's point - This feature doesn't influence the default text selection colors. As for your subsequent question/concern: >>It does feel odd / wrong to expose an inconsistent colors between AccentColor >>/ Highlight and form controls / selection... The consistent behavior between these 2

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Hi all, Thanks for the thorough review! I've opened a GitHub issue for the remaining request. Hopefully we'll settle on an option before the next Audio Working Group meeting on 5/15! I'll update the spec as soon as we do. Thanks, Evan On W

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

Hi Liang, https://chromestatus.com/metrics/feature/timeline/popularity/5356 is already somewhat high, but it is also an upper bound on the risk and probably not reflective of how many sites will be broken. Looking at a sample of sites that hit the use counter and seeing what the impact of the chan

Re: [blink-dev] Web-Facing Change PSA: Predictable reported storage quota

LGTM1 % question below. If the API is returning an approximate value, is there an increased risk of sites trying to allocate up to the amount the browser is claiming they have, and then not being able to successfully use it? Or is that already a risk and this intent does not increase it? On Mon,

Re: [blink-dev] Intent to Ship: Short-circuiting var(), attr()

LGTM3; +1 to Yoav's thanks re: the thorough analysis. On Wednesday, May 7, 2025 at 7:59:03 AM UTC-7 Yoav Weiss wrote: > LGTM2 > > Thank you for the thorough analysis!! Let's break this vicious cycle! > (before it's too late) > > On Wednesday, May 7, 2025 at 4:38:43 PM UTC+2 Daniel Bratell wrote:

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

Thanks Evan and Jeff. Evan: if we can get to API symmetry, I think that will help considerably. Evan/Jeff: this seems like good advice from the TAG. When do we think we can get the bikeshed repain...er...develop updated names? Best, Alex On Wednesday, May 7, 2025 at 12:12:29 AM UTC-7 Jeffrey

Re: [blink-dev] Intent to Extend Experiment: Shared Array Buffers, Atomics and Futex APIs

LGTM I hope it works. /Daniel On 2025-05-07 16:01, Chromestatus wrote: Contact emails v...@chromium.org, cl...@chromium.org Explainer None Specification https://tc39.github.io/ecma262/#sec-sharedarraybuffer-objects Design docs https://developer.mozi

Re: [blink-dev] Intent to Ship: Short-circuiting var(), attr()

LGTM2 Thank you for the thorough analysis!! Let's break this vicious cycle! (before it's too late) On Wednesday, May 7, 2025 at 4:38:43 PM UTC+2 Daniel Bratell wrote: LGTM1 And now I've learned about impossible things you can (or could) do with CSS. I'm not sure that was a good thing. /Danie

Re: [blink-dev] Re: Intent to Ship: CSS Custom Functions (@function)

LGTM2 /Daniel On 2025-05-06 20:36, Mike Taylor wrote: Thanks for the updates. LGTM1 On 5/6/25 4:41 AM, Anders Hartvoll Ruud wrote: See updates inline: On Wed, Feb 26, 2025 at 10:10 PM Anders Hartvoll Ruud wrote: Note that this was targeting the M136 release, so we would have ha

Re: [blink-dev] Intent to Ship: Short-circuiting var(), attr()

LGTM1 And now I've learned about impossible things you can (or could) do with CSS. I'm not sure that was a good thing. /Daniel On 2025-05-07 11:12, Anders Hartvoll Ruud wrote: Contact emails andr...@chromium.org Explainer When designing the if()

[blink-dev] Intent to Extend Experiment: Shared Array Buffers, Atomics and Futex APIs

Contact emails v...@chromium.org, cl...@chromium.org Explainer None Specification https://tc39.github.io/ecma262/#sec-sharedarraybuffer-objects Design docs https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer Summary Adds the JavaScript type S

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: System accent color for accent-color property.

On Tue, May 6, 2025 at 5:00 PM Joey Arhar wrote: > Text selection colors are not affected, I just tested it out with > experimental web platform features enabled on Canary. > > I agree that it would be nice to expose these colors in > AccentColor/AccentColorText, but the fingerprinting concern as

[blink-dev] Intent to Ship: Short-circuiting var(), attr()

Contact emails andr...@chromium.org Explainer When designing the if() function, we (CSSWG) decided to make it short-circuiting , such that we can stop evaluation once a matching condition is fo

[blink-dev] Intent to Extend Experiment: ServiceWorkerStaticRouterTimingInfo

Contact emailssuzukike...@chromium.org, yyanagis...@chromium.org Explainer https://github.com/WICG/service-worker-static-routing-api/blob/main/resource-timing-api.md SpecificationDraft ServiceWorker spec change: https://github.com/w3c/ServiceWorker/pull/1769 Summary Adds timing information for

Re: [blink-dev] Intent to Implement and Ship: Integrity Policy for scripts

To close the loop, the feature is now enabled (and aiming for M138). I also have a SW usecounter CL going. On Friday, May 2, 2025 at 11:24:58 PM UTC+2 Chris H

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: On-device Web Speech API

FYI, the TAG finished our review with https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2853142041. We were generally happy with the design decisions that Evan and the WG have made, but we were still concerned that "ondevice-only" excludes some choices that future UAs might reasonab