We are holding this feature off from M121 stable because of an unexpected
regression: https://crbug.com/1508176
While we investigate the problem, we will enable the feature through
finch on M121 Dev, Canary and Beta and watch for bug reports. We don't see
a way to measure the risk without
LGTM3
On 11/15/23 11:16 AM, Chris Harrelson wrote:
LGTM2
On Wed, Nov 15, 2023 at 7:52 AM Yoav Weiss wrote:
LGTM1
I agree that the compat risk here seems low, and the interop win
more than makes up for it.
On Monday, November 13, 2023 at 4:04:02 PM UTC+1 Mustaq Ahmed wrote:
LGTM2
On Wed, Nov 15, 2023 at 7:52 AM Yoav Weiss wrote:
> LGTM1
>
> I agree that the compat risk here seems low, and the interop win more than
> makes up for it.
>
> On Monday, November 13, 2023 at 4:04:02 PM UTC+1 Mustaq Ahmed wrote:
>
>> Hi Chris:
>>
>> The other 5 review categories are now
LGTM1
I agree that the compat risk here seems low, and the interop win more than
makes up for it.
On Monday, November 13, 2023 at 4:04:02 PM UTC+1 Mustaq Ahmed wrote:
> Hi Chris:
>
> The other 5 review categories are now green, the last one was marked a few
> hours ago.
>
> Please let me
Hi Chris:
The other 5 review categories are now green, the last one was marked a few
hours ago.
Please let me know if anything else is needed for the Blink approval
process. We are targeting M121.
Mustaq
On Thu, Nov 2, 2023 at 12:07 PM Chris Harrelson
wrote:
> It will be after you click
It will be after you click the button to start an API owners review. Also
don't forget to start the other 5 review categories.
On Thu, Nov 2, 2023 at 9:01 AM Mustaq Ahmed wrote:
> Hi Chris:
>
> https://chromestatus.com/feature/6266812908175360 is the new entry for
> this feature (because
Hi Chris:
https://chromestatus.com/feature/6266812908175360 is the new entry for this
feature (because feature type is read-only). The review bits should now be
visible to API Owners, please let know if that's not the case.
Mustaq
On Fri, Oct 27, 2023 at 5:03 PM Chris Harrelson
wrote:
> Hi
Hi Mustaq,
"web developer facing change to existing code" is meant for "bugfix-level
changes to web APIs", which is why it only requires a PSA (sorry for the
confusion - this has been a common issue and the chromestatus team is
working on improved UI to be less confusing).
In your case you are
Hi Mike:
Through our offline discussion I learned that for "web developer facing
change to existing code", the new intent process requires merely a "PSA"
without (perhaps) any need for additional approvals. I changed the email
template subject here from "PSA" to "I2S" only to secure "API Owners"
Hi Mustaq,
Please take a moment to request the other review bits (API OWNERs will
wait until those are in progress to begin our review). See
https://groups.google.com/a/chromium.org/g/blink-dev/c/bqvB1oap0Yc/m/YlO8DEHgAQAJ
for more info.
thanks!
Mike
On 10/19/23 3:41 PM, Mustaq Ahmed
Contact emailsmus...@chromium.org, fla...@chromium.org
Specificationhttps://www.w3.org/TR/uievents/#events-mouseevent-event-order
Summary
After an event target gets removed from the DOM, the logical target of the
pointer as implied by the Pointer and Mouse boundary events (i.e. over,
out, enter
11 matches
Mail list logo
