Go for it!
API owners approval is not tied to any particular milestone.
On Mon, Apr 14, 2025 at 12:22 PM Noam Rosenthal
wrote:
> Thanks!
> FYI, I'm ready to ship this in M137, I thought it was going to take longer!
> Please let me know if there are any issues with doing so.
>
> On Mon, Apr 14,
Contact emails
alcoo...@chromium.org
Explainer
https://github.com/immersive-web/depth-sensing/blob/main/explainer.md
Specification
https://immersive-web.github.io/depth-sensing
Summary
Exposes several new mechanisms to customize the behavior of the depth sensing
feature within a WebXR sessi
"Deprecate" means that the feature still works but using it shows a
deprecation warning in the DevTools console and kicks Reporting API.
IMO, we should have a deprecation period for one or two milestones. The
usage is low, but the feature removal would be critical for affected sites.
On Tue, Apr
FYI, the TAG left comments at
https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2803693504
.
On Fri, Apr 4, 2025 at 10:22 AM Evan Liu wrote:
> Are you thinking it might be reasonable to ship in M128 (decide by branch
>> on Apr 28, plan to merge any required changes before May 21
Thank you all!
I've sent emails to 2 sites which were affected.
Regarding deprecation period, I will wait for 2 weeks to hear back from
those 2 sites. If I don't get any response, then I plan to just deprecate
this feature in M138 since usage is very low.
Let me know if y'all think I should inste
Hello,
Is there a crbug tracking implementation of this feature?
Thanks
Kevin
From: Mike Taylor
Sent: Thursday, April 3, 2025 5:38 AM
To: Ashley Gullen ; Chromestatus
Cc: blink-dev@chromium.org; antoniosart...@google.com; dr...@google.com;
mk...@google.com; riz...@google.com; ta...@google.c
Contact emails
dome...@chromium.org, fer...@chromium.org, kenjibah...@chromium.org,
a...@chromium.org, memm...@chromium.org, christin...@chromium.org
Explainer
https://github.com/WICG/translation-api/blob/main/README.md
Specification
https://webmachinelearning.github.io/translation-api
Summar
Thanks!
FYI, I'm ready to ship this in M137, I thought it was going to take longer!
Please let me know if there are any issues with doing so.
On Mon, Apr 14, 2025 at 7:17 PM Chris Harrelson
wrote:
> LGTM3
>
> On Mon, Apr 14, 2025 at 11:17 AM 'Daniel Clark' via blink-dev <
> blink-dev@chromium.or
Sorry this has fallen off my radar a bit. I’m not sure I’m going to have time
to get this resolved soon, so perhaps this can be considered paused unless
anyone else is able to pick it up?
On Mon, 14 Apr 2025, at 7:09 PM, Alex Russell wrote:
> How's it going? Any updates?
>
> On Monday, March 17
Any updates here?
On Tuesday, March 18, 2025 at 7:34:04 PM UTC-7 Domenic Denicola wrote:
> On Tuesday, March 18, 2025 at 8:39:21 AM UTC+9 Robbie McElrath wrote:
>
> Contact emails
>
> rmcelr...@chromium.org, ze...@chromium.org
>
> Explainer
>
> https://github.com/WICG/controlled-frame/blob/main/R
Thanks for filing an extension request.
Some questions that weren't clear from the above:
- Is this extension going to involve breaking changes? I saw the TAG's
feedback from last year had API shape suggestions, so curious to know if
it's evolving further in this extension
- Has th
LGTM3, contingent on an official standards position disposition from
Mozilla (but not blocking on what it is).
On Monday, April 14, 2025 at 7:13:00 AM UTC-7 Corentin Wallez wrote:
> We don't have minutes for these out-of-band meetings, but we want a stable
> reference that we can point at as we
LGTM3
On Mon, Apr 14, 2025 at 11:17 AM 'Daniel Clark' via blink-dev <
blink-dev@chromium.org> wrote:
> For the record, the TAG did review this (Resolution: satisfied):
> https://github.com/w3ctag/design-reviews/issues/1033. LGTM2.
>
>
>
> -- Dan
>
>
>
> *From:* Domenic Denicola
> *Sent:* Sunday,
For the record, the TAG did review this (Resolution: satisfied):
https://github.com/w3ctag/design-reviews/issues/1033. LGTM2.
-- Dan
From: Domenic Denicola
Sent: Sunday, April 13, 2025 10:00 PM
To: Noam Rosenthal
Cc: Domenic Denicola ; blink-dev
Subject: [EXTERNAL] [blink-dev] Re: Intent to i
We're now targeting M138 to give us more time to improve the spec.
There hasn't been any spec progress in the last 2 weeks due to some
unfortunately timed vacations, but I'll be picking that up again starting
today and responding to feedback from Reilly and Dominic.
On Monday, April 14, 2025 at
Assuming these proposed metrics land in time to ship, LGTM1
On Wednesday, March 12, 2025 at 8:12:47 AM UTC-7 Mike Taylor wrote:
> These proposed metrics sound reasonable to us, so long as they capture all
> cases where the behavior is changing. But we defer to you and your team as
> the experts
How's it going? Any updates?
On Monday, March 17, 2025 at 11:39:47 AM UTC-7 Keith Cirkel wrote:
> None yet, I’ve got to rework some of the internals but got a little busy.
> I’ll hopefully have some updates in the coming weeks!
>
> On Mon, 17 Mar 2025, at 6:07 PM, Alex Russell wrote:
>
> Any upd
We don't have minutes for these out-of-band meetings, but we want a stable
reference that we can point at as well. From talking with the Mozilla
engineers working on WebGPU, this would require our API owners to talk with
their standard folks to come to some agreement there (though I don't know
18 matches
Mail list logo
