[blink-dev] Intent to Prototype: Language support for CanvasTextDrawingStyles

Contact emails schen...@chromium.org Explainer https://github.com/whatwg/html/pull/10873 Specification https://github.com/whatwg/html/pull/10873 Summary The DOM element, like all DOM elements, accepts a `lang` attribute that is used to define language specific treatment for font selection

Re: [EXTERNAL] [blink-dev] Intent to Ship: Add MediaStreamTrack support to the Web Speech API

Regarding interop support, this change was discussed at TPAC 2024 this year and was supported by Eric Carlson from Apple and Paul Adenot from Mozilla among others. I've submitted requests for formal permissions from Mozilla and WebKit

Re: [blink-dev] Intent to Prototype & Ship: scroll-start-target

LGTM3. On Wed, Dec 18, 2024 at 4:08 PM Mike Taylor wrote: > LGTM2 > On 12/18/24 3:11 PM, Chris Harrelson wrote: > > LGTM1 > > On Mon, Dec 16, 2024 at 2:10 PM David Awogbemila > wrote: > >> The CSS working group resolved >>

Re: [blink-dev] Intent to Ship: Protected Audience (B&A) - Private Aggregation & downsampling forDebuggingOnly reporting

Can you let us know when you have landed WPTs? On 12/17/24 3:44 PM, Paul Jensen wrote: Contact emails pauljen...@chromium.org qingxi...@google.com Explainer For original Protected Audience Private Aggregation reporting support: https://github.com/WICG/turtledove/pull/386

Re: [blink-dev] Intent to Prototype & Ship: scroll-start-target

LGTM2 On 12/18/24 3:11 PM, Chris Harrelson wrote: LGTM1 On Mon, Dec 16, 2024 at 2:10 PM David Awogbemila wrote: The CSS working group resolved   to make some changes based on TAG feedback. The property is

Re: [blink-dev] Intent to Prototype & Ship: scroll-start-target

LGTM1 On Mon, Dec 16, 2024 at 2:10 PM David Awogbemila wrote: > The CSS working group resolved > to > make some changes based on TAG feedback. The property is now named > "scroll-initial-target" and its keywords are "none

Re: [blink-dev] Intent to Ship: Protected Audience: Auction Nonce Hardening

Responses inline On Tuesday, December 3, 2024 at 9:03:22 PM UTC-5 Vladimir Levin wrote: On Mon, Nov 25, 2024 at 9:15 AM 'Orr Bernstein' via blink-dev < blink-dev@chromium.org> wrote: Contact emails o...@google.com, pauljen...@chromium.org, carai...@chromium.org Explainer https://github.com/W

Re: [blink-dev] Intent to Ship: Document-Policy: expect-no-linked-resources

LGTM1 to ship, with some non-blocking homework. Could you please do the work to add a DevTools Issue so developers are aware when this hint is harming performance rather than helping? It would also be good to try to do some HTTP Archive queries (or have a use counter, if that's feasible) to h

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

On Wed, Dec 18, 2024 at 5:32 PM Mike Taylor wrote: > We discussed this in our OWNERs meeting, and agreed this should be an I2S > that requires 3LGTMs to ship. But, we can just use this thread - no need to > send more mail. Some other folks have other questions, but I'll let them > send them indep

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

We discussed this in our OWNERs meeting, and agreed this should be an I2S that requires 3LGTMs to ship. But, we can just use this thread - no need to send more mail. Some other folks have other questions, but I'll let them send them independently. On 12/13/24 12:57 PM, Mike Taylor wrote: Tha

Re: [blink-dev] Intent to Ship: Protected Audience (B&A) - Selectable Reporting IDs

LGTM2 On Wed, Dec 18, 2024 at 7:44 AM Mike Taylor wrote: > LGTM1 - feature parity makes sense between Chrome & Chrome/B&A. > On 12/16/24 9:07 AM, Paul Jensen wrote: > > > > On Fri, Dec 13, 2024 at 1:09 PM Mike Taylor > wrote: > >> Hey Paul, >> >> The UX of reviewing multiple PRs without the sur

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

On Wed, Dec 18, 2024 at 10:46 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > Thanks for working on this!! :) > > On Wednesday, December 18, 2024 at 4:33:10 AM UTC+1 ds...@google.com > wrote: > > Contact emails > > ds...@chromium.org, memm...@chromium.org > > Explainer > > https://gith

Re: [blink-dev] Intent to Ship: CSS text-box, text-box-trim and text-box-edge

Ok, so let's go! LGTM3 /Daniel On 2024-12-18 16:55, Mike Taylor wrote: I had the same question (as it was noted in the WebKit position), but found https://github.com/w3c/csswg-drafts/commit/3b15a485b2f9dfaa8e9ad3958ec2625d7857f719. I assume this I2S means we agree. :) On 12/18/24 10:39 A

Re: [blink-dev] Intent to Ship: CSS text-box, text-box-trim and text-box-edge

I had the same question (as it was noted in the WebKit position), but found https://github.com/w3c/csswg-drafts/commit/3b15a485b2f9dfaa8e9ad3958ec2625d7857f719. I assume this I2S means we agree. :) On 12/18/24 10:39 AM, Daniel Bratell wrote: The spec you link has a red note saying: "This is

Re: [blink-dev] encrypted_client_hello client extension on FQDN that does not support it

I think people on net-dev are more likely to know. Adding it as receipient and setting blink-dev as bcc. /Daniel On 2024-12-18 12:39, Haga R. wrote: Hi! I'm working on a simple tool to reproduce some JA3 Fingerprint of several client, including , of course, Chromium based browsers. With th

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

Thanks for working on this!! :) On Wednesday, December 18, 2024 at 4:33:10 AM UTC+1 ds...@google.com wrote: Contact emails ds...@chromium.org, memm...@chromium.org Explainer https://github.com/whatwg/fs/blob/main/proposals/FileSystemObserver.md Specification https://github.com/whatwg/fs/pull

Re: [blink-dev] Intent to Ship: Protected Audience (B&A) - Selectable Reporting IDs

LGTM1 - feature parity makes sense between Chrome & Chrome/B&A. On 12/16/24 9:07 AM, Paul Jensen wrote: On Fri, Dec 13, 2024 at 1:09 PM Mike Taylor wrote: Hey Paul, The UX of reviewing multiple PRs without the surrounding context is pretty bad. Could you maybe give some code e

Re: [blink-dev] Intent to Ship: CSS text-box, text-box-trim and text-box-edge

The spec you link has a red note saying: "This is an early draft of a proposal, and might change significantly as design critiques and use cases are registered and various details and interactions with other properties are worked out. Do not ship (yet)." Does that only apply to the properties

Re: [blink-dev] Intent to Ship: CSS text-box, text-box-trim and text-box-edge

LGTM2 On Wednesday, December 18, 2024 at 4:29:51 PM UTC+1 Mike Taylor wrote: > LGTM1 > On 12/11/24 11:49 AM, Koji Ishii wrote: > > Contact emails lin...@chromium.org, ko...@chromium.org > > Explainer None > > Specification https://drafts.csswg.org/css-inline-3/#text-edges > > Summary > > To achi

Re: [blink-dev] Intent to Ship: CSS text-box, text-box-trim and text-box-edge

LGTM1 On 12/11/24 11:49 AM, Koji Ishii wrote: Contact emails lin...@chromium.org, ko...@chromium.org Explainer None Specification https://drafts.csswg.org/css-inline-3/#text-edges Summary To achieve optical balance o

Re: [EXTERNAL] [blink-dev] Intent to Ship: Add MediaStreamTrack support to the Web Speech API

You also probably want to flip the relevant chromestatus review bits (for security, privacy, etc). On Wednesday, December 18, 2024 at 2:27:42 AM UTC+1 dan...@microsoft.com wrote: > The links supporting the browser Gecko and WebKit signals do not seem > strongly indicative of a current positive

[blink-dev] encrypted_client_hello client extension on FQDN that does not support it

Hi! I'm working on a simple tool to reproduce some JA3 Fingerprint of several client, including , of course, Chromium based browsers. With the latest Chromium version (Google 131), I noticed that, when establishing TLS connection, chromium still send the *encrypted_client_hello *extension des