that this intent is to allow updateIfOlderThanMs >>>> to be used in TEE. However, because TEE architecture is itself complicated, >>>> is it possible to

On Fri, Nov 29, 2024 at 7:18 AM Rick Byers wrote: > On Fri, Nov 29, 2024 at 5:02 AM Rune Lillesveen > wrote: > >> >> On Wed, Nov

Does this intent deprecate or change behavior of existing APIs, > such that it has potentially high risk for Android WebView-based > applications? > > None > > >

Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > N/A > > > Debuggability

approve an Intent to Ship like this one, we need at least a draft >> specification up for review. The link you've given here is just to an issue. >> >> I see at the

Does this intent deprecate or change behavior of existing APIs, such > that it has potentially high risk for Android WebView-based applications? > > None > > > >

LGTM1 to ship including a deprecation trial >> >> On Fri, Nov 29, 2024, 5:00 pm François Doray wrote: >> >>> >>> >>> On Friday, November

Does this intent deprecate or change behavior of existing APIs, such >>>>>> that it has potentially high risk for Android WebView-based applications? >>

>> intent is just for the X25519, since the Ed25519 is still not ready and >> needs more spec work. We all think that this work can be done as part of >> the new Web Cryptography

I have tested PRF support with a FIDO2 security key (YubiKey & Thales). It seems the PRF extension works fine on desktop Chrome, *but prf does not

Does this intent deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>

, this intent is to expose attributionsrc on where previously it >>>>> wasn't exposed, although it was already processed. It doesn't sound any >>

dev] Intent to Ship: Support creating ClipboardItem > with Promise > > > > LGTM2. > > > > I agree with Daniel's comments that a couple sentences of explainer

> This intent message was generated by Chrome Platform Status > . > > -- > You received this message because you are subscribed to the Google Groups > "blink

Does this intent deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>

an "intent to ship" but is not yet approved (or rejected), and this one >> doesn't show up there which also means that I cannot record the LGTM1 >> >>

Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > Not applicable as this

Thanks all for the comments here. > One more question - this applies to both and speculation rules, right? This *mostly* does not apply to

Hi there, Is there any progress regarding shipping FileSystemFileHandle.move()? Right now the only way to move or rename something is to copy the

API to ship assuming we > have those options written up for the TAG (and API OWNERS) to consider. > > > > LGTM1 on the condition we produce that writeup. > > Done,

scheduled to ship in M133: >>>> https://chromestatus.com/feature/5166674414927872 >>>> >>>> There does not appear to be an associated

Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >

LGTM1 to ship in M133. > > It's nice to see the explainer and design improved based on TAG > feedback, thank you for that! > > Rick > > On Tue, Nov 26, 2024 at 10

LGTM3 On 11/27/24 10:22 AM, Rick Byers wrote: > LGTM2 > > On Wed, Nov 27, 2024 at 9:40 AM Vladimir Levin > wrote: > > Thank you for

/issues/4456 resolved to allow multiple pseudo-elements in getComputedStyle. I think it would be good to ship that ideally in the same release as this, or at least not much later.

see this ship! > > I'm also terrified about how many of my tabs will want to use more than > 4GB of RAM at once for their AI models, but of course that is not a good > reason

LGTM3 On Wed, Nov 27, 2024 at 11:13 AM Yoav Weiss (@Shopify) < yoavweiss@chromium.org> wrote: > LGTM2 > > On Friday, November 22, 2024

as this Intent proposes) Expose mutation events that aren't just "some text content changed" Provide proper DOM traversal and manipulation APIs Generally be expressible

Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Goals

supposed to ship around M128, but due to > an error, it shipped on M130, which made the update process a bit harder. > > On Tue, Nov 26, 2024 at 4:42 PM Mike Taylor > wrote: >