LGTM to experiment M129-M134 inclusive.
On Tue, Jul 30, 2024 at 9:39 PM Daseul Lee wrote:
> Contact emails
>
> asu...@chromium.org, a...@chromium.org, christin...@chromium.org,
> ds...@chromium.org, memm...@chromium.org
>
> Explainer
>
> https://github.com/whatwg/fs/blob/main/proposals/FileSys
On Mon, Jul 22, 2024 at 2:53 PM Mike Taylor wrote:
> Could you also request the Enterprise bit?
>
I missed flipping the bit after filling out the enterprise survey
questions! Done.
In the meantime - I'd love to know more about `[SecureContext=flag]` not
> working - that capability was introduce
Thanks for the v2 updates.
LGTM1
On 7/30/24 2:09 PM, Reilly Grant wrote:
On Tue, Jul 16, 2024 at 1:20 PM Robbie McElrath
wrote:
Thanks - before I jump too deeply into the review, would you
mind requesting the various review gate bits in your
chromestatus entry?
D
LGTM1
On Tue, Jul 30, 2024 at 11:09 AM Reilly Grant wrote:
> On Tue, Jul 16, 2024 at 1:20 PM Robbie McElrath
> wrote:
>
>> Thanks - before I jump too deeply into the review, would you mind
>> requesting the various review gate bits in your chromestatus entry?
>>
>> Done. We've been using launch
or LGTM2 - sorry, race condition.
On 7/31/24 11:46 AM, Mike Taylor wrote:
Thanks for the v2 updates.
LGTM1
On 7/30/24 2:09 PM, Reilly Grant wrote:
On Tue, Jul 16, 2024 at 1:20 PM Robbie McElrath
wrote:
Thanks - before I jump too deeply into the review, would you
mind reque
LGTM2
On Wed, Jul 31, 2024 at 7:38 AM Mustaq Ahmed wrote:
> On Mon, Jul 22, 2024 at 2:53 PM Mike Taylor
> wrote:
>
>> Could you also request the Enterprise bit?
>>
> I missed flipping the bit after filling out the enterprise survey
> questions! Done.
>
> In the meantime - I'd love to know more
LGTM3. If it is possible to use a finch flag for this removal, please do,
but if not please keep an eye out for any regression and revert at the
first sign of trouble.
On Wed, Jul 31, 2024 at 5:49 PM Chris Harrelson
wrote:
> LGTM2
>
> On Wed, Jul 31, 2024 at 7:38 AM Mustaq Ahmed wrote:
>
>> On
On Friday, July 26, 2024 at 5:28:22 AM UTC-4 Yoav Weiss wrote:
On Mon, Jul 22, 2024 at 5:26 PM 'Maksim Orlovich' via blink-dev <
blink-dev@chromium.org> wrote:
Note: https://github.com/WICG/turtledove/pull/1230 is an updated link for
the second spec clarification pull requests, and the first o
Contact emails
pauljen...@chromium.org
Explainer
https://github.com/WICG/turtledove/blob/main/PA_real_time_monitoring.md
Specification
https://github.com/WICG/turtledove/pull/1212
Summary
The goal of real-time monitoring is to get Protected Audience API auction
monitoring data to the buye
On Tue, Jul 30, 2024 at 7:05 PM 'Adam Ettenberger' via blink-dev <
blink-dev@chromium.org> wrote:
> cc+: fla...@chromium.org, pec...@chromium.org, mahesh...@samsung.com
>
> Was wondering if you could share some background / motivation into why
> `touch-action` was selected for allowing/disallowing
I'm concerned this may not be the right property. For use cases where the
author wants to handle the pointerevents themselves (e.g. in order to
accept free-form drawing) they should be using touchaction or
preventDefault on the events to tell the browser they are handling them.
They shouldn't have
11 matches
Mail list logo
