sure how to get "developer signal" mike...@chromium.org schrieb am Dienstag, 17. Februar 2026 um 20:08:25 UTC+1: > On 2/14/26 5:48 pm, Helmut Januschka wrote: >

> According to the HTML spec, when a drag starts the user agent should send > the appropriate events to the drag source to indicate that the pointer > event stream has ended,

you planning to? We have not finalized on how this would work, and don't have concrete plans to implement anything. I think the key at this stage is to get more customer feedback.

and having to >> chan >> >> I don't know where the second half of my sentence went - but it should >> read ", and having to change the implementation

is limited to the one supported by CSSPseudoElement, yes On Friday, February 20, 2026 at 8:31:11 PM UTC+1 Vladimir Levin wrote: > I believe this depends on CSSPseudoElement from

website permission to access a powerful API (specifically Bluetooth, Camera, Clipboard, DisplayCapture, Geolocation, Microphone, Serial, and USB), their consent is intended

of things to do, but we've chosen to prioritize other LNA landing work to ensure better user experiences (see the ongoing discussion in https://groups.google.com/a/chromium

a need to delay this change in order to figure out whether and how to remove the upper limit. On Mon, Feb 23, 2026 at 3:15 AM Barry Pollard wrote: > I've not heard any push back from

introducing blur to the image in the process Note: spec wise this >>>>> is technically different than 'pixelated'. In actual implementations it is >

hard-to-address privacy conern here, but there might be a way around if we only allow a single profile to ever access this. Will ping you offline to discuss. Best, Alex On Wednesday,

TC39 proposal to add a method to sum multiple values > to JavaScript. Add an iterable-taking > `Math.sumPrecise` method which returns the sum of the > values in the iterable

> due to lack of signals from other browsers. See requests for standards >>> positions from WebKit / Firefox below. >>> >>> *Gecko*: No signal (https

being expanded to include > WebSockets. WebSockets connections to local address will now start > triggering permission prompts. All of the current LNA enterprise policies

>> to reflect this change or is this behavior implied by what's already there? >> >> >> I added a quick update to it just now (meant to do it yesterday but

indeed needs to be combined with some kind of branching/conditional > to be useful. An example without if() would be (though ultimately similar): > > color: var(--maybe

roughly equivalent to the capabilities of other APIs such as getUserMedia(). While exposing information about a user's connected peripherals raises privacy concerns, many

not going to > change. TypeScript will have to adapt accordingly. > Understood. TypeScript has recently adapted its included lib.dom.d.ts file as of the upcoming v6, which

explainer up to date? >>> >>> For all intents and purposes yes. There's maybe a couple of minor >>> additions from the spec that could be added to the

d like to understand if >>>> other browsers plan to ship this addition. >>>> >>> Thanks for the feedback. I've now filed requests for WebKit

have approval to run the experiment (I am supportive too, > FWIW), but one question below: > > Technically, niche issues remain where in serialization, with the new Rust >

re good to go, happy launching! > > On Wed, Feb 11, 2026 at 8:57 AM 'Hongchan Choi' via blink-dev > wrote: > > Thanks all for the review and approvals. > >

> needs to be opt-in. Basides, creating dummy data channels and trusting > that the remote endpoint doesn't use them isn't very eloquent. > > On Tuesday, February

this needs to be done >> before 3xLGTM and shipping. Thank you! >> >> On Fri, Feb 6, 2026 at 11:21 AM Philip Jägenstedt >> wrote: >> > LGTM1, seems

the feature to the stable >> channel slowly >> >> For this type of change this risks more confusion/breakage to >> web-developers & users vs. just letting

In addition to support for native color and depth > textures and texture arrays, it also provides support for > different layer types that are managed by the system > compositor

are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscribe

We plan to > continue to separately send out intents for other LNA rollouts. > > On Mon, Feb 2, 2026 at 12:08 PM Alex Russell > wrote: > >> So again, apologies for

> *To:* Kurt Catti-Schmidt (SCHMIDT) > *Cc:* blink-dev > *Subject:* Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: JSON > and style support for link rel=modulepreload

class has to be specifically within the shadow tree to work, despite the element bearing the class being an ancestor of both of them? Oh, dear... Not very intuitive. Thank you for the

I tend to agree that the I2S is not the right place for this debate. Seeing no open issues for the API on the spec / PR, and reading TAG's guidance that adding APIs on the global is at least