> This PR is still getting pretty active review comments. At least some of
them seem like they'll impact the behavior. Do you think it would be
reasonable to wait for the PR to settle before approving? I don't think we
necessarily need to wait for formal approval or merging, but it seems like
right
I agree with Domenic about TAG risk; just flagging this as part of the
larger package is great.
Will the rollout of this change be Finch controlled? Do you expect the
launch to happen over a single release? If you do a partial rollout for
compat reasons and it goes sideways, please let us know.
LGTM3
On Fri, Oct 11, 2024 at 3:12 PM Chris Harrelson
wrote:
> LGTM2
>
> I think it makes sense at this point to start finching/turning on this API
> freely on the stable channel, in order to inform the final spec
> language and landed PR. This is also the main risk factor identified in the
> Mo
LGTM2
I think it makes sense at this point to start finching/turning on this API
freely on the stable channel, in order to inform the final spec
language and landed PR. This is also the main risk factor identified in the
Mozilla standards position request.
I think this is inherently a chicken-and
On Fri, Oct 11, 2024 at 8:30 PM Alex Russell
wrote:
> Hey Rune,
>
> It's surprising that there aren't any developer signals given that we're
> going first and there are no signals from other vendors and that there's no
> explainer with a compelling code example that shows how this solves an
> imp
Contact emails
agpa...@google.com, gui...@google.com
Explainer
None
Specification
https://w3c.github.io/mediacapture-output/#dom-mediadevices-selectaudiooutput
Summary
This API prompts the user to select a specific audio output device. This API
allows the user to select an audio output devi
We've also published this post with details and our rollout plans:
https://developer.chrome.com/docs/web-platform/bfcache-ccns#how_chrome_is_changing_this_behavior
On Wed, 25 Sept 2024 at 06:25, 'Mingyu Lei' via blink-dev <
blink-dev@chromium.org> wrote:
> Hi Erwin,
>
> We have now decided to rol
Hey Alan,
Was there useful developer feedback from the first OT besides the lack of
these features? Or are most potential testers waiting on the sidelines
until these arrive?
Also, will this be a compatible extension? That is, will code that worked
in the previous version continue to work with
Is Apple is pushing back on caret animation for battery life reasons? Do we
share that concern?
Best,
Alex
On Thursday, October 10, 2024 at 6:17:12 AM UTC-7 Chromestatus wrote:
> Contact emails schen...@chromium.org
>
> Explainer https://drafts.csswg.org/css-ui/#caret-animation
> https://git
Hey Rune,
It's surprising that there aren't any developer signals given that we're
going first and there are no signals from other vendors and that there's no
explainer with a compelling code example that shows how this solves an
important problem (although I think I can imagine what it is). Ca
10 matches
Mail list logo
