blink-dev

Contact emails sche...@chromium.org Explainer https://github.com/whatwg/html/pull/10873

(With my TAG hat on) Could the shipping of this feature be held until 3/18? We have discussed the

(With my TAG hat on) Could the shipping of this feature be held until 3/18? We have discussed the

Contact emails fut...@chromium.org, se...@chromium.org Explainer https://github.com/w3c/csswg-drafts

Given your example, it seems like `video/mp4;codecs="hev1.1.6.L120.90"` is supported by

AV1 is great from a quality perspective, but it is not an option for use cases that require hardware

The disable was from M128 to M130. On Friday, February 28, 2025 at 8:05:49 PM UTC Mike Taylor wrote:

This Intent is missing a lot of fields we usually require: Explainer Specification Motivation TAG

@Domenic, thanks for your feedback, I just updated the milestones. Regards the CSSWG current status

+1 that providing temporary enterprise policy exceptions is standard practice for breaking changes

LGTM3 On 3/2/25 9:51 PM, TAMURA, Kent wrote: LGTM2. On Mon, Mar 3, 2025 at 11:34 AM Domenic Denicola

@Muyao Thanks for your updates on this! Today I've found a new version of the Keyboard Lock

Done, requested reviews. On Sunday, March 2, 2025 at 9:35:30 PM UTC-5 Domenic Denicola wrote: Can you

On Fri, Feb 28, 2025 at 10:18 PM 'Dan Clark' via blink-dev <blin...@chromium.org>

On Monday, March 3, 2025 at 5:35:10 PM UTC+9 Domenic Denicola wrote: LGTM3, thanks for all the work

LGTM3 On Friday, February 28, 2025 at 1:55:26 AM UTC+9 Mike Taylor wrote: LGTM2 On 2/27/25 11:51 AM,

LGTM2. I'm saddened by the way the implementer community has not been able to converge upon and

Hey Reema, Very sorry that you've been on hold here. Thank you for doing some manual

I appreciate your perspective on this, Emilio. I don't understand the norms around comments in

Contact emails rou...@chromium.org Specification https://w3c.github.io/payment-request/

> What are the spec implementations of this change? I don't believe that the spec requires a

By missing the end, I mean this: const ob = new Observable((subscriber) => { subscriber.next(1);

Thanks for the detailed response! It's quite a handful, but given the explanation you gave, would

This has been submitted as https://chromiumdash.appspot.com/commit/

An update, Mozilla has confirmed at https://github.com/web-platform-tests/interop/issues/855 that the

Created PR to move issue warning https://github.com/w3c/csswg-drafts/pull/11794 On Tuesday, February

On Thu, Feb 27, 2025 at 1:41 AM 'Dan Clark' via blink-dev <blin...@chromium.org>

On Thu, Feb 27, 2025 at 6:05 AM Vladimir Levin <vmp...@chromium.org> wrote: On Wed, Feb 26,

Note that this was targeting the M136 release, so we would have had another month to tweak this

Thanks! I was syncing with our PM/TPM to provide the best answer of the enterprise questions. Now