CSS > to access the system accent color specified on the user's device. This > allows developers to apply native app like styling to their web content in > contexts where

approving this to ship before the PRs landed. Can you point us to the spec discussion that led to the name change? On Thu, Apr 9, 2026 at 4:11 AM Keita Suzuki wrote: > *Contact emails

I missed to share the issue link of mozilla position I created. https://github.com/mozilla/standards-positions/issues/1372 Thank you! 2026년 4월 9일 목요일 AM 12시 7분 24초 UTC+9에 vmp.

t plans to do so, as the CSS Color spec already anticipates > this kind of mitigation. In the system color section > (apologies, I > should've linked this in the I2S), it

allow developers to define float >>> exclusion shapes using rectangle coordinates, aligning Chrome with Firefox >>> and Safari which already support this feature

were three ship blockers >> identified and now addressed: >> [Tag Review] - Quota vs. context window >> >> [Tag Review] - Interoperable model parameters

we should ship this now, so LGTM3. Of course we should continue to look at user feedback, UXR and developer feedback to ensure we're striking a great experience for users here (as

m happy to leave > it to you to follow up and get wpt.fyi green. LGTM3 > > On Thu, Apr 2, 2026 at 4:56 AM Yoshisato Yanagisawa < > yyanagisawa@chromium.org> wrote: >

Sorry to be somewhat off-topic here, but I failed to get the first message on this thread (so the initial intent message itself) to my mailbox. This has happened multiple times in the

, nice to see this community effort. LGTM3 On Wed, Apr 1, 2026 at 11:19 AM Yoav Weiss (@Shopify) < yoavweiss@chromium.org> wrote: > LGTM2 !! > > On Wednesday, April 1

xrequire you to back it out/pause the launch. On 3/31/26 10:12 am, Barry Pollard wrote: > I've just discovered this was never shipped by default. I can't see a > reason

I plan to leave the metrics after shipping, and will see how it will be for a while. 2026年3月30日(月) 20:11 Philip Jägenstedt : > LGTM2, thanks for the OT findings summary. It's encouraging

> *To:* Rune Lillesveen > *Cc:* blink-dev > *Subject:* [EXTERNAL] Re: [blink-dev] Intent to Ship: CSS Name-only > Container Queries > > Sounds close to a bugix

devices configured to expose wired serial ports will return non-empty lists of serial ports. All other devices will always return empty lists. On Wed, Mar 25, 2026 at 1:47 PM Reilly

did try to probe for developer interest but couldn't get much: See these posts and their replies: - https://www.linkedin.com/posts/patrickbrosset_if-you-use-a-service

the Explainer to consider for future efforts: >> >> - it's great to see the considered alternatives; thank you! >> - Explainers are "speaking design

has tried to write those formulae > themselves has failed at least once so there was good value for > implementations to provide the builtin (and overflow safety checks). >

the tests to WPT! >> >> On Wed, Mar 25, 2026 at 10:45 AM Dominik Röttsches >> wrote: >> >>> Philip asked me a few questions, here are the details: >

> LGTM to continue with your new plan. > > On Tue, Mar 17, 2026 at 1:59 PM Philip Jägenstedt > wrote: > >> Hi again, >> >> This has not shipped yet, because

fundamentally necessary to prevent the "Web Lock footgun," where a long-lived worker could hold a lock indefinitely. (Please see: https://github.com/whatwg/html

makes sense to file a Firefox bug >> so they could also make this fix. >> >> -- Dan >> >> On Tuesday, March 17, 2026 at 12:55:03 PM UTC-7 Pranav Modi wrote

are likely to become outdated at some point — without heavy caveats for anyone depending on them! To take learnings from a similar historic adage on this subject, 640k was never going

> wishes to transfer cookies or other state they'd have to do so themselves > (since migration is limited to same-site cases I believe you could use an > iframe or similar

the spec to call into > the Fetch monkey patch, and other general spec and WPT work in the past few > weeks. > > Good luck with the roll out! > On 3/11/26 5:56 pm, Chris Thompson

of things to meet the quality bar we > require for shipping. > On 3/6/26 11:49 am, Hubert Chao wrote: > > More WPTs are in, for the 3 types of workers (dedicated, service, and

this lead to a regression (of weird "used to work" mime type configs) see: https://issues.chromium.org/issues/492024623 here is a fix: https://chromium-review.googlesource

quick PSA to let you know that we are restoring the > isConditionalMediationAvailable() static method to the base Credential > interface. > > * Background:* > Credential

the implementation to match CSSWG >> resolutions. >> >> *Contact emails* >> kbabbitt@microsoft.com >> >> *Explainer* >> >>

I missed to update those entries earlier. I have updated the entries yesterday. ________________________________ From: Philip Jägenstedt Sent: Wednesday, March 11, 2026 9:13

> option to select when the position has been filed but there hasn't yet been > a response. > The actual ChromePlatformStatus entry reflects the correct status for that