Re: [blink-dev] Intent to Ship: Auto range support for font descriptors inside @font-face rule

2022-10-24 Thread Yoav Weiss
LGTM3 I think there's some interop risk here if Apple and Mozilla won't add support for explicit "auto" values and developers would start using them, but I agree that there's no real incentive for developers to do so. On Mon, Oct 24, 2022 at 4:47 PM Mike Taylor wrote: > LGTM2 > > On 10/19/22

Re: [blink-dev] Intent to Ship: Private Network Access preflight requests for subresources

2022-10-24 Thread José Luis Campanello
Hi all, i've been working to fix an application that will be affected by PNA preflights (we have an application that talks to a private server and a local -127.0.0.1- server). As I understood from this blog post

Re: [blink-dev] Re: FYI Privacy Sandbox Ads APIs origin trial

2022-10-24 Thread Josh Karlin
This week, no sooner than October 26, we will begin increasing the Privacy Sandbox Relevance and Measurement origin trial population towards 5% of Chrome Stable users for Attribution Reporting and Topics APIs. You can expect to see traffic levels increase over a period of a few days. Pre-stable

Re: [blink-dev] Intent to Ship: Align Timers (including DOM timers) at 125 Hz

2022-10-24 Thread Mike Taylor
Thanks Etienne. LGTM1 to ship - good luck with the rollout. On 10/20/22 12:18 PM, Etienne Pierre-doray wrote: Have we asked Mozilla for a signal? I haven't asked for a signal. I can ask but this feels N/A; this change is Web facing but remains spec-compliant, and I don't think we want

Re: [blink-dev] Intent to Ship: Align Timers (including DOM timers) at 125 Hz

2022-10-24 Thread Mike Taylor
On 10/20/22 11:39 AM, Olli Pettay wrote: On 10/20/22 18:23, Mike Taylor wrote: On 10/19/22 8:05 PM, Etienne Pierre-doray wrote: /Gecko/: No signal Have we asked Mozilla for a signal? I don't think so. I could say we're interested in trying to reduce wake-ups, but it is unclear how this

Re: [blink-dev] Intent to Ship: Auto range support for font descriptors inside @font-face rule

2022-10-24 Thread Mike Taylor
LGTM2 On 10/19/22 8:38 AM, Philip Jägenstedt wrote: Thanks Munira for the detailed explanation, and thanks for filing the Gecko and WebKit bugs! I think that from a web developer's point of view, this won't be a feature that you actively use, but sensible defaults and the lack of a

Re: [blink-dev] Intent to Experiment: Back/forward cache NotRestoredReason API

2022-10-24 Thread Mike Taylor
Cool - thanks for the info and for updating the explainer. On 10/24/22 2:09 AM, Yuzu Saijo wrote: Thanks Mike! I update the description in the explainer. We talked to the privacy team and decided to say "Extensions" for all the extension related reasons (we decided that it's okay to expose

[blink-dev] Re: Intent to Ship: Increased max nesting level for setTimeout(0)

2022-10-24 Thread Etienne Pierre-doray
> > 2.1 is the new version. We can ignore 2.0. > I suppose this doesn't need to be released on M108 then. I'll keep experimenting. On Fri, Oct 21, 2022 at 4:36 PM Hannes Payer wrote: > > > On Fri, Oct 21, 2022 at 12:31 PM Etienne Pierre-doray < > etien...@chromium.org> wrote: > >> Is that a

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

2022-10-24 Thread Yoav Weiss
I think it makes sense to flip it on now, and turn it off if printing NG gets reverted. On Mon, Oct 24, 2022 at 9:14 AM Frédéric Wang wrote: > Hello, > > Reading [1], I don't think any distinction between pure blink features or > UI/browser features for "feature freeze". I understand the only

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

2022-10-24 Thread Frédéric Wang
Hello, Reading [1], I don't think any distinction between pure blink features or UI/browser features for "feature freeze". I understand the only requirement is to have code complete, but probably turning on the flag after the branch point is fine. However [2] also mentions "Two weeks prior

Re: [blink-dev] Intent to Experiment: Back/forward cache NotRestoredReason API

2022-10-24 Thread 'Yuzu Saijo' via blink-dev
Thanks Mike! I update the description in the explainer. We talked to the privacy team and decided to say "Extensions" for all the extension related reasons (we decided that it's okay to expose the presence of extensions, but will avoid giving any further information). Yuzu On Fri, Oct 21, 2022