[blink-dev] Re: Intent to Ship: import.meta.resolve()

LGTM1 This seems like a small and useful addition, that has reasonable consensus behind it. On Thursday, June 30, 2022 at 6:13:33 AM UTC+2 Domenic Denicola wrote: > Contact emailsdome...@chromium.org > > Explainerhttps://gist.github.com/domenic/f2a0a9cb62d499bcc4d12aebd1c255ab > > Specification

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

LGTM to experiment M104-M105. On Tue, Jul 5, 2022 at 3:30 PM Etienne Pierre-doray wrote: > Contact emailsetien...@chromium.org > > ExplainerNone > > Specification > https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html > > Design docs > > https://docs.google.com/document/d/1boT0k8B

Re: [blink-dev] Re: Intent to Ship: import.meta.resolve()

LGTM2 On 7/6/22 4:50 AM, Yoav Weiss wrote: LGTM1 This seems like a small and useful addition, that has reasonable consensus behind it. On Thursday, June 30, 2022 at 6:13:33 AM UTC+2 Domenic Denicola wrote: Contact emails dome...@chromium.org Explainer ht

Re: [blink-dev] Re: Intent to Ship: import.meta.resolve()

LGTM3 /Daniel On 2022-07-06 15:07, Mike Taylor wrote: LGTM2 On 7/6/22 4:50 AM, Yoav Weiss wrote: LGTM1 This seems like a small and useful addition, that has reasonable consensus behind it. On Thursday, June 30, 2022 at 6:13:33 AM UTC+2 Domenic Denicola wrote: Contact emails

[blink-dev] Upcoming chromestatus.com home page change

Hello blink-dev, I wanted to give everyone a heads up that what you’ll see when you visit chromestatus.com about a week from now will change from being the “All features” view to the “Roadmap” view. This change is to give visitors who are not intimately involved in the development of Chromium a mo

Re: [blink-dev] Intent to Prototype & Ship: Syntax changes to markup based Client Hints delegation

LGTM1 to ship this *and* remove the old syntax at the same time. We/I think it'd be better to do it all at once without having both syntaxes in the while for a period. On Wed, Jun 29, 2022 at 12:15 PM Mike Taylor wrote: > To add some clarity to the proposed changes and the rationale (as this > c

[blink-dev] Question regarding webrtc

Hello Blink, I am working on a project in which we are using an audio call feature of WebRTC. Audio call works fine. On button click we need to enable share screen and replaceTracks with share screen track only, but replaceTrack web api replaces tracks of same kind, for example audio track can

Re: [blink-dev] Intent to Prototype & Ship: Syntax changes to markup based Client Hints delegation

LGTM2 (including removing the old syntax which is not yet used enough to be a compatibility problem) /Daniel On 2022-07-06 17:38, Chris Harrelson wrote: LGTM1 to ship this *and* remove the old syntax at the same time. We/I think it'd be better to do it all at once without having both syntaxes

Re: [blink-dev] Question regarding webrtc

the discuss-webrtc list is probably a better place to ask in the future. Adding video to an audio-only call will, by design, require renegotiation. There is a sample for that at https://webrtc.github.io/samples/src/content/peerconnection/upgrade/ - it a

[blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

Contact emailsdba...@chromium.org ExplainerNone Specificationhttps://www.w3.org/TR/css-values-3/#custom-idents Summary The CSS keyword 'default' is not allowed within CSS custom identifiers, which are used for many types of user-defined names in CSS (for example, names created by @keyframes rul

[blink-dev] Re: Intent to Ship: User Agent Client Hints GREASE Update

As a small update, we recently encountered a few instances of leading special characters causing issues (1 ,2 ) with sites. Accordingly, we slightly modified the spec

Re: [blink-dev] Intent to Deprecate and Remove: CSS default keyword is disallowed in custom identifiers

On Wed, Jul 6, 2022 at 9:50 PM David Baron wrote: > Contact emailsdba...@chromium.org > > ExplainerNone > > Specificationhttps://www.w3.org/TR/css-values-3/#custom-idents > > Summary > > The CSS keyword 'default' is not allowed within CSS custom identifiers, > which are used for many types of use