Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

tervention doesn't really make sense in modern day browsers, and neither blink or webkit are spec compliant (in distinct ways). On Fri, Mar 22, 2024 at 2:57 PM Mike Taylor wrote: On 3/22/24 1:37 AM, Yoav Weiss (@Shopify) wrote: On Thu, Mar 21, 2024 at 10:11 AM Zheda Chen wr

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

in comparison. Let me know if you have any other questions. Thanks, Akash On Wednesday, March 20, 2024 at 8:30:31 AM UTC-7 Mike Taylor wrote: On 3/18/24 7:17 PM, 'Akash Nadan' via blink-dev wrote: Contact emails akash...@google.com, lin...@chromium.org, john...@chromium.org Explainer

Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

On 3/22/24 1:37 AM, Yoav Weiss (@Shopify) wrote: On Thu, Mar 21, 2024 at 10:11 AM Zheda Chen wrote: The privacy/security/enterprise/debuggability gates are requested on Chrome Status. Testing gate to be requested later. Thanks - we've been asked to not send LGTMs until all bits have

Re: [blink-dev] Intent to Ship: SVG context-fill and context-stroke

LGTM1 On 3/18/24 10:53 AM, Mike Taylor wrote: Thanks on both fronts, Stefan! On 3/15/24 8:37 PM, Stefan Zager wrote: On Fri, Mar 15, 2024 at 6:29 AM Mike Taylor wrote: On 3/14/24 6:29 PM, Stefan Zager wrote: On Thu, Mar 14, 2024, 3:13 PM Mike Taylor wrote: On 3/14

Re: [blink-dev] Intent to Ship: CSS view-transition-class and class VT argument syntax

LGTM1 On 3/20/24 2:27 PM, Vladimir Levin wrote: Contact emails vmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-classes.md Specification

Re: [blink-dev] Intent to Experiment: Skip Preload Scanning

Could you also please request review for Privacy, Security, and Debuggability in your chromestatus entry? On 3/22/24 1:57 PM, Mike Taylor wrote: On 3/21/24 7:24 PM, Alex N. Jose wrote: > What milestones are you requesting for the Origin Trial? M125 to M131 Thanks - LGTM to experimen

Re: [blink-dev] Intent to Experiment: Skip Preload Scanning

On 3/21/24 7:24 PM, Alex N. Jose wrote: > What milestones are you requesting for the Origin Trial? M125 to M131 Thanks - LGTM to experiment 6 milestones from M125 to M130 inclusive (which I think is what you asked for!). On Thu, Mar 21, 2024 at 2:44 PM Mike Taylor wrote: Hi A

Re: [blink-dev] Intent to Experiment: Skip Preload Scanning

Hi Alex, What milestones are you requesting for the Origin Trial? thanks, Mike On 3/21/24 3:18 PM, Alex N. Jose wrote: Contact emails ale...@chromium.org Explainer https://docs.google.com/document/d/1wiaTL5TeONTZamycMVMjo76nMcbhHNYznQy7I_zCVRY/edit?usp=sharing

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

LGTM2. Good luck! On 3/20/24 4:30 PM, Yoav Weiss (@Shopify) wrote: LGTM1 On Wed, Mar 20, 2024 at 8:35 PM David Adrian wrote: > What's our plan to mitigate that risk? Slow rollout? Enterprise policy? Both? Something else entirely? We also worked with a variety of vendors to fix

Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

You should be able to see all the various bits for approvals in your chromestatus entry now, can you fill them out please? There have been a few questions/comments about the lack of clarity of what "unimportant cross-origin frames" are. What exactly is the definition? You mention that Safari

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate the includeShadowRoots argument on DOMParser

On 3/19/24 6:51 PM, Mason Freed wrote: On Tue, Mar 19, 2024 at 1:44 PM Mike Taylor wrote: Hi Mason, Would you mind requesting reviews for the various shipping gates (privacy, security, enterprise, etc.) in your chromestatus entry? Definitely! But I only need to do

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

On 3/18/24 7:17 PM, 'Akash Nadan' via blink-dev wrote: Contact emails akashna...@google.com , lin...@chromium.org , johni...@chromium.org Explainer Attribution Reporting with event-level reports

Re: [blink-dev] Intent to Deprecate and Remove: Deprecate the includeShadowRoots argument on DOMParser

Hi Mason, Would you mind requesting reviews for the various shipping gates (privacy, security, enterprise, etc.) in your chromestatus entry? On 3/15/24 6:49 PM, Mason Freed wrote: Contact emails mas...@chromium.org Explainer None

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

Also, would you mind requesting reviews for the various shipping gates (privacy, security, enterprise, etc.) in your chromestatus entry? On 3/19/24 12:34 PM, Yoav Weiss (@Shopify) wrote: On Mon, Mar 18, 2024 at 3:37 PM 'David Adrian' via blink-dev wrote: Contact emails

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

It would also be helpful to discuss what breakage looks like in this case. Would it be a one-time loss of state (i.e., have to log in again), or something different? On 3/19/24 5:08 AM, Yoav Weiss (@Shopify) wrote: OK, so just to summarize my understanding: * We expect this to have some

Re: [blink-dev] Intent to Ship: SVG context-fill and context-stroke

Thanks on both fronts, Stefan! On 3/15/24 8:37 PM, Stefan Zager wrote: On Fri, Mar 15, 2024 at 6:29 AM Mike Taylor wrote: On 3/14/24 6:29 PM, Stefan Zager wrote: On Thu, Mar 14, 2024, 3:13 PM Mike Taylor wrote: On 3/14/24 1:17 PM, Stefan Zager wrote: /WebKit

Re: [blink-dev] Intent to Ship: Document picture-in-picture: add option to hide back-to-tab button

Thank you! LGTM2 On 3/15/24 1:13 PM, Tommy Steimel wrote: Got it, thanks! Adding one in crrev.com/c/5375045 <http://crrev.com/c/5375045> On Fri, Mar 15, 2024 at 7:51 AM Mike Taylor wrote: If a human can observe the expected behavior by clicking on a button and noticing th

Re: [blink-dev] Intent to Ship: Document picture-in-picture: add option to hide back-to-tab button

? On Fri, Mar 15, 2024 at 6:15 AM Mike Taylor wrote: Is there any reason to not convert https://steimelchrome.github.io/document-pip/hide-back-to-tab-button.html into a manual WPT <https://web-platform-tests.org/writing-tests/manual.html>? Manual tests aren't

Re: [blink-dev] Intent to Ship: SVG context-fill and context-stroke

On 3/14/24 6:29 PM, Stefan Zager wrote: On Thu, Mar 14, 2024, 3:13 PM Mike Taylor wrote: On 3/14/24 1:17 PM, Stefan Zager wrote: Contact emails sza...@chromium.org Explainer None Specification https://svgwg.org/svg2-draft

Re: [blink-dev] Intent to Ship: Document picture-in-picture: add option to hide back-to-tab button

Is there any reason to not convert https://steimelchrome.github.io/document-pip/hide-back-to-tab-button.html into a manual WPT ? Manual tests aren't ideal, but something seems better than nothing. On 3/14/24 9:42 PM, Domenic Denicola

Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

The privacy and security teams review all intents, so requesting reviews and answering the relevant questionnaires is the best path forward. Looking forward to the new I2S - thanks! On 3/14/24 11:22 AM, Zheda Chen wrote: More details are updated in ChromeStatus, including interoperability and

Re: [blink-dev] Intent to Ship: SVG context-fill and context-stroke

On 3/14/24 1:17 PM, Stefan Zager wrote: Contact emails sza...@chromium.org Explainer None Specification https://svgwg.org/svg2-draft/painting.html#context-paint Summary Implements an existing SVG feature that allows the keywords 'context-fill' and

Re: [blink-dev] Re: Intent to Ship: 'writingsuggestions' attribute

LGTM2 On 3/14/24 12:43 AM, Domenic Denicola wrote: Awesome! LGTM1. On Thu, Mar 14, 2024 at 1:35 PM 'Stephanie Zhang' via blink-dev wrote: Thanks for clarifying! Updated the Chrome Status' "Finch Feature Name" field to kWritingSuggestions and removed the "Non-finch

Re: [blink-dev] Intent to Experiment: WebAssembly JS String Builtins

they will be added before phase 3 >>as required by the proposal process. >> >> Let me know if you have any further questions! >> >> Best regards, >> Emanuel >> >> On Tue, Mar 12, 2024 at 3:52 PM Mike Taylor >> wrote: >> >&

Re: [blink-dev] Intent to Ship: WebGPU: ServiceWorker and SharedWorker support

aufort' via blink-dev wrote: On Tue, Mar 12, 2024 at 6:58 PM Mike Taylor wrote: On 3/11/24 4:06 PM, 'François Beaufort' via blink-dev wrote: Contact emails

Re: [blink-dev] Intent to Ship: Protected Audience: Downsampled forDebugOnly & Increase number of component ads

LGTM2 On 3/13/24 11:45 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Monday, March 11, 2024 at 4:21:36 PM UTC-4 Paul Jensen wrote: On Wed, Mar 6, 2024 at 12:07 PM Yoav Weiss (@Shopify) wrote: On Mon, Mar 4, 2024 at 7:00 PM Paul Jensen wrote: On Wed, Feb

Re: [blink-dev] Intent to Ship: WebGPU: ServiceWorker and SharedWorker support

On 3/11/24 4:06 PM, 'François Beaufort' via blink-dev wrote: Contact emails fbeauf...@google.com Explainer None Could you write a few sentences why this is a useful addition? Specification https://gpuweb.github.io/gpuweb/#navigator-gpu Summary

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

On Wed, Mar 6, 2024 at 10:21 AM Yoav Weiss (@Shopify) wrote: On Mon, Mar 4, 2024 at 9:36 PM Mike Taylor wrote: LGTM1 On 3/4/24 1:33 PM,

Re: [blink-dev] Intent to Experiment: WebAssembly JS String Builtins

Hi Emanuel, For OTs, we can approve extensions for 3 milestones at a time, depending on the criteria set at https://www.chromium.org/blink/launching-features/#origin-trials. Would you mind summarizing progress in the various areas? It sounds like there is good engagement from the "spec

Re: [blink-dev] Intent to Ethe xperiment: Document Subtitle (Fix PWA app titles)

Cool - LGTM to experiment from M124 to M127 inclusive (I think that's what you requested - feel free to correct me if not). later, Mike On 3/11/24 3:47 PM, 'Diego Gonzalez' via blink-dev wrote: Hola Mike, We're looking art M124 for 4 milestones. 落 Diego On Wednesday 6 March 2024 at

Re: [blink-dev] Intent to Ship: RegExp duplicate named capture groups

On 3/11/24 6:49 AM, Yoav Weiss (@Shopify) wrote: On Fri, Mar 8, 2024 at 4:26 PM Mike Taylor wrote: LGTM1 On 3/7/24 6:22 PM, Shu-yu Guo wrote: Contact emails pth...@chromium.org, s...@chromium.org Explainer None Specification

Re: [blink-dev] Re: Intent to Experiment: IP Protection Phase 0

Hi Daniel, We don't have any further details to announce right now, but when we do we can update this thread. thanks, Mike On 3/8/24 7:28 PM, Daniel Santiago Rincón Silva wrote: Hi Brianna and team. I see that the readme has been updated to specify that the feature will be initially

Re: [blink-dev] Intent to Extend Experiment: Extending Storage Access API (SAA) to non-cookie storage

I'm recused on this one, but even with the extension to 125, you're still not going beyond the default 6 milestones for an OT (the original request was for 120 to 124) - so the approval should be fairly trivial. On 3/6/24 11:31 AM, Ari Chivukula wrote: Contact emails aric...@chromium.org

Re: [blink-dev] Intent to Ship: RegExp duplicate named capture groups

LGTM1 On 3/7/24 6:22 PM, Shu-yu Guo wrote: Contact emails pth...@chromium.org, s...@chromium.org Explainer None Specification https://github.com/tc39/ecma262/pull/2721 Summary https://github.com/tc39/proposal-duplicate-named-capturing-groups

Re: [blink-dev] Re: Intent to Ship: Document Render-Blocking

LGTM1 On 3/6/24 11:00 AM, Vladimir Levin wrote: Re failing tests: The flag is currently in "test" status  which I

Re: [blink-dev] Intent to ship: MP4 container support for MediaRecorder

rg wrote: On Tue, Feb 27, 2024 at 1:45 AM Mike Taylor wrote: On 2/22/24 9:21 PM, 'Sunggook

Re: [blink-dev] Intent to Ethe xperiment: Document Subtitle (Fix PWA app titles)

Hey Diego, Can you clarify what milestones you're requesting for the OT? thx, Mike On 2/21/24 11:16 AM, 'Diego Gonzalez' via blink-dev wrote: Hola Manuel, Thanks for the heads up. In order for this to be an HTML PR, it requires interest from another vendor

Re: [blink-dev] Intent to Ship: Private Aggregation debug mode for auctionReportBuyers reporting

LGTM2 On 3/6/24 5:39 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Thu, Feb 29, 2024 at 7:29 PM Alex Turner wrote: Contact emails ale...@chromium.org Explainer

Re: [blink-dev] Intent to Ship: Compute Pressure

On 3/5/24 6:57 AM, Mandy, Arnaud wrote: Contact emails kenneth.r.christian...@intel.com, arnaud.ma...@intel.com, wei4.w...@intel.com, raphael.kubo.da.co...@intel.com Explainer https://github.com/w3c/compute-pressure/blob/main/README.md Specification

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

LGTM1 On 3/4/24 1:33 PM, Nicolás Peña wrote: Contact emails n...@chromium.org Explainer https://github.com/fedidcg/FedCM/issues/428 Specification https://github.com/fedidcg/FedCM/pull/547

Re: [blink-dev] Intent to Experiment: Add JavaScript timer wake up alignment for unimportant cross-origin frames

My concern is going from 1% to 50% on stable - if something does go wrong, that's a _lot_ of folks who will experience it. Are you open to something smaller like 5%? If not, why not? thx On 2/29/24 12:34 AM, Zheda Chen wrote: The volume of data on Beta is too low to draw any conclusion.

Re: [blink-dev] Intent to Ship: Used color scheme root scrollbars

Thanks for the summary of the experiment results on Edge - sounds positive. If this is purely a browser UI change, then we don't really need the blink-dev process at all. However, if we're relying on concepts defined in a CSSWG draft, and devs can change the outcome w/ some CSS (or maybe

Re: [blink-dev] Intent to Ship: Used color scheme root scrollbars

Hi there, Would you mind requesting reviews for the various review gates in your chromestatus entry? On 2/29/24 4:12 PM, 'Yaroslav Shalivskyy' via blink-dev wrote: Contact emails gerch...@microsoft.com , yshalivs...@microsoft.com

Re: [blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

ported in the Android API. Thanks, Nan On Mon, Feb 26, 2024 at 1:53 PM Mike Taylor wrote: Hi Akash, Could you please clarify: if WebView supports the web API (which it does, IIUC?), these new features also be supported in the WebView context, correct? I'm not able to find

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

(non-owner hat on) - Thanks for flagging, Domenic. We'll re-ping the thread once we decide if we should rename it, and to what. On 2/28/24 9:43 PM, Domenic Denicola wrote: I've raised a potentially-breaking spec issue which I'd like to get a conclusion on before LGTMing this:

Re: [blink-dev] Intent to Ship: Form Controls Support Vertical Writing Mode Direction Support

LGTM2 On 2/28/24 9:37 PM, Domenic Denicola wrote: With my HTML editor hat on, I can confirm the spec PR looks good and only has editorial issues left. It fell between the cracks for 2 weeks; apologies for that. With my API Owner hat on, LGTM1. There are a few borderline aspects here: *

Re: [blink-dev] Intent to Experiment: Add JavaScript timer wake up alignment for unimportant cross-origin frames

Could you say more why you would like to experiment on 50% of stable, vs requesting permission to ship? That's quite a leap from 1% - and it seems you already have results demonstrating performance improvements. Also, mind answering the question of specifying "unimportant frames"? On 2/27/24

Re: [blink-dev] Intent to Experiment: FedCM multi IDP in single get() call

Could you please request reviews for the privacy/security/debuggability review gates in your chromestatus entry? On 2/21/24 3:21 PM, Nicolás Peña wrote: Contact emails n...@chromium.org Explainer The Federated Credential Management (FedCM) API currently only allows one identity provider

Re: [blink-dev] Intent to Experiment: Add JavaScript timer wake up alignment for unimportant cross-origin frames

Hello, To clarify: is this intended to be an I2E, or a Developer Trial? According to https://chromestatus.com/feature/5106220399853568, it appears you are in the dev trial stage. But you mention stable experiment below... so perhaps that's a process mistake? Can you give more info on the

Re: [blink-dev] Intent to ship: MP4 container support for MediaRecorder

On 2/22/24 9:21 PM, 'Sunggook Chue' via blink-dev wrote: Contact emails sung...@microsoft.com dalecur...@chromium.com (reviewer and mentor). Explainer https://www.w3.org/TR/mediastream-recording/ Specification

Re: [blink-dev] Intent to Experiment: FedCM Button Mode API and Use Other Account API

That said, please request approvals from the various review gates in your chromestatus entry before experimenting. On 2/26/24 7:41 PM, Mike Taylor wrote: LGTM to experiment from M124 to M127 inclusive. On 2/26/24 5:45 PM, Yi Gu wrote: Contact emails * y

Re: [blink-dev] Intent to Experiment: FedCM Button Mode API and Use Other Account API

LGTM to experiment from M124 to M127 inclusive. On 2/26/24 5:45 PM, Yi Gu wrote: Contact emails * y...@chromium.org, cbiesin...@chromium.org, tanzach...@chromium.org * Explainer *

Re: [blink-dev] Intent to Ship: ServiceWorker static routing API

LGTM3 On 2/26/24 5:39 PM, Domenic Denicola wrote: LGTM2 On Tue, Feb 27, 2024 at 1:33 AM Chris Harrelson wrote: I see the main spec PR has landed and a small related Fetch PR is done. Thanks all for doing that! LGTM1 On Tue, Feb 13, 2024 at 8:55 PM Domenic Denicola

Re: [blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

Hi Akash, Could you please clarify: if WebView supports the web API (which it does, IIUC?), these new features also be supported in the WebView context, correct? I'm not able to find where the Attribution Reporting API is _disabled_ for WebView (assuming it would be in

Re: [blink-dev] Problem chrome after upgrade to 122

Hello, Could you please file a bug at crbug.com/new, with steps to reproduce and (ideally) a publicly accessible URL? It's not obvious what "big-IP Technology" is. thanks, Mike On 2/26/24 5:48 AM, argane jalal wrote: hi, I have application exécute with big-IP Technology this application

Re: [blink-dev] Intent to Prototype and Ship: Standardized CSS zoom

Thanks for the feedback Noam - would you mind filing a bug at crbug.com/new that contains some steps to reproduce the breakage, and possibly some affected codepaths and report back here? Agree that breaking Excel is not a great outcome. On 2/26/24 10:01 AM, Noam Helfman wrote: Great to see

Re: [blink-dev] Intent to Ship: CSSImportRule.styleSheet

On 2/23/24 8:31 AM, Amos Lim wrote: Contact emails eui-sang@samsung.com Explainer None Would you mind explaining why this is a useful addition for developers? Or is the motivation improved spec compliance? Specification

Re: [blink-dev] Re: Intent to Ship: RTCIceCandidate url and relayProtocol attributes

LGTM2 On 2/19/24 11:34 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Wed, Feb 14, 2024 at 7:29 PM Philipp Hancke wrote: Am Mi., 14. Feb. 2024 um 16:09 Uhr schrieb Yoav Weiss (@Shopify) : On Monday, February 12, 2024 at 7:52:17 PM UTC+1 philipp...@googlemail.com

Re: [blink-dev] Intent to Ship: Shadow root clonable attribute

LGTM1 to ship (see below). On 2/15/24 6:12 PM, Mason Freed wrote: Contact emails mas...@chromium.org Explainer None Specification https://dom.spec.whatwg.org/#shadowroot-clonable Summary This enables individual control over whether a shadow root is

Re: [blink-dev] Intent to Ship: CSS picture-in-picture display mode

LGTM3 On 2/16/24 6:21 AM, Manuel Rego Casasnovas wrote: Thanks for adding the test. LGTM2. Cheers,   Rego On 14/02/2024 13:15, 'François Beaufort' via blink-dev wrote: On Wed, Feb 14, 2024 at 10:48 AM Manuel Rego Casasnovas mailto:r...@igalia.com>> wrote:     On 14/02/2024 10:46,

Re: [blink-dev] Intent to Ship: CSS paint-order for non-SVG text

LGTM3, with the same conditions from Chris. On 2/15/24 6:15 PM, Chris Harrelson wrote: LGTM2, conditioned on also making the tests Rego mentioned non-tentative. On Mon, Feb 12, 2024 at 11:05 AM Stefan Zager wrote: Done (requested N/A). On Mon, Feb 12, 2024 at 3:05 AM Manuel Rego

Re: [blink-dev] Intent to Ship: Zstd Content-Encoding

LGTM3 On 2/15/24 1:39 PM, Chris Harrelson wrote: LGTM2 On Wed, Feb 14, 2024 at 7:11 PM Nidhi Jaju wrote: On Thu, Feb 15, 2024 at 12:50 AM David Benjamin wrote: On Wed, Feb 14, 2024 at 9:20 AM Yoav Weiss (@Shopify) wrote: LGTM1 On

Re: [blink-dev] Intent to Ship: Private Network Access permission to relax mixed content

LGTM2 On 2/15/24 4:55 AM, Yoav Weiss (@Shopify) wrote: LGTM1 On Thu, Feb 15, 2024 at 9:51 AM 'Yifan Luo' via blink-dev wrote: OT findings: https://docs.google.com/spreadsheets/d/15b2kCikEqw6P0xZFXQKMiKk_WnqnIZpT5p8nmLgc93Y/edit?usp=sharing There are 7 OT users and most of them

Re: [blink-dev] Re: Intent to Ship: WebSocketStream

Thank you - LGTM1 On 2/15/24 7:16 AM, Adam Rice wrote: Thanks Mike, I have requested the approvals. Sorry for the delay, I didn't understand the interface. Adam On Thu, 15 Feb 2024 at 01:39, Mike Taylor wrote: Hi Adam, Would you mind requesting approvals in the chromestatus

Re: [blink-dev] Re: Intent to Ship: Document picture-in-picture: allow Window's focus() API to focus opener

LGTM3 On 2/15/24 1:06 AM, Yoav Weiss (@Shopify) wrote: LGTM2 On Wed, Feb 14, 2024 at 9:28 PM Chris Harrelson wrote: Thanks! LGTM1 On Wed, Feb 14, 2024 at 11:07 AM 'Tommy Steimel' via blink-dev wrote: Landed the PR and added a comment to the TAG thread. Thanks!

Re: [blink-dev] Intent to Ship: Support in Chrome for the VoiceIsolation getUserMedia constraint

LGTM3 On 2/14/24 11:49 AM, Chris Harrelson wrote: LGTM2 On Wed, Feb 14, 2024 at 8:46 AM Philip Jägenstedt wrote: LGTM1, some comments inline. On Sat, Feb 3, 2024 at 6:15 AM Per Åhgren wrote: >> >> >> TAG review status >> >> Issues addressed >> This is

Re: [blink-dev] Re: Intent to Ship: WebSocketStream

Hi Adam, Would you mind requesting approvals in the chromestatus entry for the various review gates? On 2/8/24 1:30 AM, Adam Rice wrote: Unfortunately, no partners were ready when we did the OT, so there was no feedback at all. However, we have subsequently received private feedback that

Re: [blink-dev] Intent to Ship: jitterBufferTarget

Thanks! I had intended to reply that it's very simple to add a runtime enabled feature to IDL, but it's been a busy day. :) On 2/13/24 3:57 PM, Eldar Rello wrote: >Can we add a flag? https://chromium.googlesource.com/chromium/src/+/main/docs/flag_guarding_guidelines.md >(Or someone can

Re: [blink-dev] Intent to Ship: Cross App and Web Attribution Measurement

pect we'll eventually add support). On 2/8/24 11:59 PM, Nan Lin wrote: Hi Yoav, On Thu, Feb 8, 2024 at 11:09 PM Yoav Weiss (@Shopify) wrote: On Wed, Feb 7, 2024 at 12:58 PM Nan Lin wrote: Thanks Mike. On Wed, Feb 7, 2024 at 12:50 AM Mike Taylor wrote:

Re: [blink-dev] Intent to Ship: jitterBufferTarget

We also need to flip the various review gates on the chromestatus entry (privacy, security, enterprise... etc.). If you're working with someone at Google on this feature, perhaps they could assist? On 2/12/24 9:53 AM, Mike Taylor wrote: On 2/12/24 6:36 AM, Eldar Rello wrote

Re: [blink-dev] Intent to Ship: jitterBufferTarget

On 2/12/24 6:36 AM, Eldar Rello wrote: Contact emails eldar.re...@gmail.com Explainer None Specification https://w3c.github.io/webrtc-extensions/#dom-rtcrtpreceiver-jitterbuffertarget Summary JitterBufferTarget attribute allows applications to specify

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

On Wed, Feb 7, 2024 at 1:59 PM Brad Triebwasser wrote: +blink-dev@chromium.org <mailto:blink-dev@chromium.org> / Reply All Thanks for your feedback, Mike! Recipes inline: On Tue, Feb 6, 2024 at 9:36 PM Mike Taylor wrote: Hi Brad,

Re: [blink-dev] Intent to Prototype and Ship: Private network access checks for navigation requests: warning-only mode

: LGTM2 On Fri, Feb 2, 2024 at 11:10 PM Mike Taylor wrote: Correction: LGTM1, conditioned on requesting Enterprise, Debuggability, and Testing bits in chromestatus. :) On 2/2/24 5:09 PM, Mike Taylor wrote: LGTM1 On 2/2/24

Re: [blink-dev] Intent to Ship: Cross App and Web Attribution Measurement

On 2/6/24 3:59 AM, Nan Lin wrote: Hi Mike, Thanks for reviewing. Please see responses inline. Nan On Mon, Feb 5, 2024 at 9:33 PM Mike Taylor wrote: Hi Nan, On 2/2/24 5:00 AM, Nan Lin wrote: Contact emails lin...@chromium.org <mailto:lin...@chromium.

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

Hi Brad, On 2/6/24 3:49 PM, Brad Triebwasser wrote: Contact emails btri...@chromium.org Explainer https://github.com/w3c/window-management/blob/main/EXPLAINER_spec_and_permission_rename.md

Re: [blink-dev] Intent to Ship: Cross App and Web Attribution Measurement

Hi Nan, On 2/2/24 5:00 AM, Nan Lin wrote: Contact emails lin...@chromium.org , johni...@chromium.org Explainer Cross App and Web Attribution Measurement

Re: [blink-dev] Intent to Prototype and Ship: Private network access checks for navigation requests: warning-only mode

Correction: LGTM1, conditioned on requesting Enterprise, Debuggability, and Testing bits in chromestatus. :) On 2/2/24 5:09 PM, Mike Taylor wrote: LGTM1 On 2/2/24 11:17 AM, Jonathan Hao wrote: Contact emails p...@chromium.org Explainer https://github.com/WICG/private

Re: [blink-dev] Intent to Prototype and Ship: Private network access checks for navigation requests: warning-only mode

LGTM1 On 2/2/24 11:17 AM, Jonathan Hao wrote: Contact emails p...@chromium.org Explainer https://github.com/WICG/private-network-access/blob/main/explainer.md Specification https://wicg.github.io/private-network-access Design docs

Re: [blink-dev] Intent to Ship: 'pagereveal' event

LGMT2 - no concerns about lack of a response from TAG. On 2/2/24 1:18 AM, Domenic Denicola wrote: LGTM1 On Fri, Feb 2, 2024 at 6:53 AM David Bokan wrote: Contact emails bo...@chromium.org, khushalsa...@chromium.org, nrosent...@chromium.org, vmp...@chromium.org

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

: Thanks for marking it for review! I submitted a request to review this change to the chromium enterprise mailing list. Thanks, Thomas On Wed, Jan 31, 2024 at 1:08 PM Mike Taylor wrote: Yep - seems

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

ed to take some extra action, and a "Feature deprecation" entry is the only way we can flag that. On Wed, Jan 31, 2024 at 5:44 PM Mike Taylor wrote: Gentle reminder to follow up on requesting privacy/security/debuggability approvals in chromestatus

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Gentle reminder to follow up on requesting privacy/security/debuggability approvals in chromestatus (which is currently blocking LGTMs). On Wednesday, January 24, 2024 at 7:23:28 AM UTC-5 Mike Taylor wrote: > Would you mind requesting reviews for the various gates (privacy, > se

Re: [blink-dev] Intent to Ship: CSS light-dark() Color Function

LGTM2 On 1/30/24 1:11 PM, Chris Harrelson wrote: LGTM1 On Tue, Jan 30, 2024 at 10:08 AM Rune Lillesveen wrote: Contact emails futh...@chromium.org Explainer None Specification https://drafts.csswg.org/css-color-5/#light-dark

Re: [blink-dev] Intent to Ship: NavigationActivation

On 1/29/24 2:44 AM, 'Noam Rosenthal' via blink-dev wrote: On Friday, January 26, 2024 at 5:15:28 PM UTC Vladimir Levin wrote: On Fri, Jan 26, 2024 at 4:27 AM Noam Rosenthal wrote: Finch feature nameNone Non-finch justification It's a web-API, exposing it

Re: [blink-dev] PSA: Protected Audience k-Anonymity Enforcement

then that auction will return without a winner. Protected Audience auctions already return with no winner in some cases, such as when there are no bids, so this does not introduce a new behavior. On Fri, Jan 26, 2024 at 4:24 AM Mike Taylor wrote: Hi Russ, Can you say more about

Re: [blink-dev] Intent to Ship: Private Network Access permission to relax mixed content

Hi! Could you please request the various approval bits for the review gates in your chromestatus entry? On 1/26/24 11:07 AM, 'Yifan Luo' via blink-dev wrote: Contact emails l...@chromium.org, cl...@chromium.org Explainer

Re: [blink-dev] Intent to Ship: Support in Chrome for the VoiceIsolation getUserMedia constraint

Hi Per, On 1/26/24 8:27 AM, Per Åhgren wrote: Contact emails p...@chromium.org Explainer None Specification https://w3c.github.io/mediacapture-extensions/#voiceisolation-constraint Summary This is about adding support in Chrome for the VoiceIsolation

Re: [blink-dev] PSA: Protected Audience k-Anonymity Enforcement

Hi Russ, Can you say more about the compatibility implications for such a change? AFAIU, things shouldn't "break" for users or throw errors behind the scenes, correct? thanks, Mike On 1/26/24 12:59 AM, 'Russ Hamilton' via blink-dev wrote: We plan to start enabling the k-anonymity

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

Yep - that is an official positive signal, thanks! On 1/24/24 7:40 PM, Francis McCabe wrote: Does this: https://mozilla.github.io/standards-positions/#wasm-js-promise-integration count as an official positive signal? Francis On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) wrote:

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

LGTM2 On 1/24/24 4:10 PM, Rick Byers wrote: Great, thank you! Yep, looks like the PR is about to land to me, I'm satisfied. LGTM1 On Wed, Jan 24, 2024 at 10:02 AM Paul Jensen wrote: That spec PR has now been reviewed and approved by the Protected Audience team and our spec mentor. 

Re: [blink-dev] Intent to Ship: Long Animation Frame Timing

LGTM1 On 1/17/24 9:32 AM, 'Noam Rosenthal' via blink-dev wrote: Updating that Mozilla gave an official positive signal: https://github.com/mozilla/standards-positions/pull/962 Updated the corresponding chromestatus field. On Monday, January 15, 2024 at 10:34:19 AM UTC Noam Rosenthal wrote:

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Would you mind requesting reviews for the various gates (privacy, security, debuggability) for an OT/DT in your chromestatus entry? On 1/19/24 10:43 PM, Thomas Guilbert wrote: Contact emails tguilb...@chromium.org Explainer None Specification

Re: [blink-dev] Re: Intent to Ship: Allow for WebAuthn credential creation in a cross-origin iframe

f we get any reply :) On Wed, 17 Jan 2024 at 10:25, Mike Taylor wrote: I think erring on the side of requesting a signal here is a good idea. :) On 1/17/24 8:33 AM, Stephen Mcgruer wrote: API owners: It wasn't clear

Re: [blink-dev] Intent to Extend Experiment: Soft Navigation Heuristics

LGTM to extend to 123 inclusive. On 1/22/24 10:00 PM, Ian Clelland wrote: Contact emails iclell...@chromium.org Explainer https://bit.ly/soft-navigation https://docs.google.com/document/d/1eUyQg3YLEmYjrTMC3p-F1MilECwCynhM6WIbIo05SPU/edit Specification

Re: [blink-dev] Intent to Ship: Allow Cross-Origin Subframes to Send Automatic Beacons

Thanks Liam. This seems fine to me given that both parties need to opt in. LGTM1 On 1/22/24 6:10 PM, Liam Brady wrote: Hi Mike, "crossOrigin=true" is just a typo. "crossOrigin" was the original naming convention for "crossOriginExposed". It was renamed during code review, but I forgot to

Re: [blink-dev] New API owner: Domenic Denicola

+1 - congrats! I look forward to Domenic bringing his decade plus of web and standards experience to the group. (I think it was somewhere between 2010-2012 that I first saw Domenic give a talk at the NYC.js meetup and have been a fan since). On 1/21/24 4:24 AM, Yuki Shiino wrote:

[blink-dev] Re: Intent to Ship: New ALPS code point

In our OWNERS meeting this week, there was some confusion on what's being proposed here (which is understandable, this isn't quite a typical intent for web exposed feature). Here's a summary of what we're trying to accomplish: 1) We shipped support for the ACCEPT_CH frame over h2 and h3 back

Re: [blink-dev] Intent to Ship: Allow Cross-Origin Subframes to Send Automatic Beacons

Hi Liam, On 1/16/24 3:49 PM, 'Liam Brady' via blink-dev wrote: Contact emails lbr...@google.com , shivani...@chromium.org , jkar...@chromium.org Explainer(s)

Re: [blink-dev] Intent to Ship: RTCRtpSender setParameters() extensions for requesting the generation of a key frame

LGTM2 On 1/19/24 12:41 PM, Chris Harrelson wrote: LGTM1 On Fri, Jan 19, 2024 at 7:36 AM 'Vladimir Levin' via blink-dev wrote: Thank you for the detailed explanation. It's hard to decipher from meeting notes whether a discussion is bikeshedding or serious objections :)

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

On Tue, Oct 17, 2023 at 12:42 AM Mike Taylor wrote: LGTM1 On 10/15/23 11:07 AM, 'Sahir Vellani' via blink-dev wrote: Thanks for the feedback, I wasn't aware they

<    1   2   3   4   5   6   7   8   9   >