[blink-dev] Intent to Implement and Ship: Fullscreen Capability Delegation

Contact emails mus...@chromium.org, m...@chromium.org Explainer https://github.com/WICG/capability-delegation Specification https://wicg.github.io/capability-delegation/spec.html (Work in progress for fullscreen algorithm change: https://github.com/WICG/capability-delegation/pull/28) Design doc

[blink-dev] PSA: Chrome will start ignoring touch-action changes at pointerdown, again!

Summary: Chrome will soon ignore any changes to touch-action done at a pointerdown event handler until the end of current touch-gesture, fully matching the spec and other major browsers again. Details crbug.com/1314739 The PointerEvents spec requires the browser to ignore any changes

Re: [blink-dev] Intent to Experiment: Capability Delegation with Payment Request

ri, Aug 27, 2021 at 2:53 AM Yoav Weiss wrote: > Apologies for missing this! This fell off of our collective radar :/ > > What's the requested timeline for experimentation? > > On Fri, Aug 13, 2021 at 5:50 PM Mustaq Ahmed wrote: > >> Contact emails >> >> mus

[blink-dev] Intent to Ship: Capability Delegation with Payment Request

Contact emails mus...@chromium.org, smcgr...@chromium.org Explainer https://github.com/WICG/capability-delegation Specification https://wicg.github.io/capability-delegation/spec.html Design doc https://docs.google.com/document/d/1IYN0mVy7yi4Afnm2Y0uda0JH8L2KwLgaBqsMVLMYXtk/edit?usp=sharing Summ

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

been left out by UKM. In case this is still needed, we are rolling out the 1% Stable experiment that we promised on Jan 17. Mustaq On Wed, Mar 6, 2024 at 10:06 AM Mustaq Ahmed wrote: > No, issue 327409885 is related to the PSA on canceling mousedown in iframe > <https://groups.goo

[blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

Contact emailsmus...@chromium.org ExplainerNone Specificationhttps://w3c.github.io/pointerevents/#pointerevent-interface Summary The Pointer Events Working Group made PointerEvent.getCoalescedEvents() restricted to secure contexts 4+ years ago, which removed the API from insecure contexts. Chro

Re: [blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

ty/blink/renderer/bindings/IDLExtendedAttributes.md#securecontext On Tue, Jul 16, 2024 at 9:30 PM Domenic Denicola wrote: > > > On Wed, Jul 17, 2024 at 6:52 AM Mustaq Ahmed wrote: > >> Contact emailsmus...@chromium.org >> >> ExplainerNone >> >> Specificationhttps

[blink-dev] Web-Facing Change PSA: Coalesced/predicted events in untrusted PointerEvents will retain original targets

Contact emailsmus...@chromium.org Specification https://w3c.github.io/pointerevents/#populating-and-maintaining-the-coalesced-and-predicted-events-lists Summary For untrusted (i.e. JS constructed) PointerEvents, the events returned by PointerEvent.getCoalescedEvents() and PointerEvent.getPredict

Re: [blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

On Wed, Jul 17, 2024 at 2:20 PM Mike Taylor wrote: > On 7/17/24 10:18 AM, Mustaq Ahmed wrote: > > > Can you ask for WebKit's position? Or maye there's at least a pointer > to working group discussions they participated in? > > - Safari doesn't yet support Poin

Re: [blink-dev] Web-Facing Change PSA: Coalesced/predicted events in untrusted PointerEvents will retain original targets

; > yoavwe...@chromium.org> wrote: > >> >> >> On Fri, Jul 26, 2024 at 5:04 PM Rick Byers wrote: >> >>> >>> >>> On Fri, Jul 26, 2024 at 7:37 AM Yoav Weiss (@Shopify) < >>> yoavwe...@chromium.org> wrote

Re: [blink-dev] Intent to Ship: Remove PointerEvent.getCoalescedEvents() from insecure contexts

It's a bit scary doing this without a Finch flag, but the usage is > very low and such pages are already broken in Firefox. > > On Fri, Jul 19, 2024 at 1:00 AM Mustaq Ahmed wrote: > >> >> >> On Wed, Jul 17, 2024 at 2:20 PM Mike Taylor >> wrote: >> >

[blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

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

Re: [blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

2023 at 10:39 AM Mike Taylor wrote: > 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 mor

Re: [blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

to be less confusing). > > In your case you are making a change that adjusts web-exposed behavior > enough that it requires an I2S. So you'll need to update the feature type > and file for all 5 review bits before the API owners can re-review. > > On Tue, Oct 24, 2023 at 9:

Re: [blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

ick 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 >> thi

[blink-dev] Intent to Ship: Interoperable mousemove default action

Contact emailsmus...@chromium.org, fla...@chromium.org ExplainerNone Specificationhttps://w3c.github.io/uievents/#event-type-mousemove Summary Canceling mousemove will not prevent text selection or drag-and-drop. Chrome allowed cancelling mousemove events to prevent other APIs like text selecti

Re: [blink-dev] Intent to ship: Interoperable Pointer and Mouse boundary events after DOM changes

nd 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. >

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

based >>> roll-out (and hitting a finch killswitch on reports of any issues) should >>> be enough to mitigate the risk. >>> >>> You might also consider enabling UKM support >>> <https://source.chromium.org/chromium/chromium/src/+/main:componen

[blink-dev] Web-Facing Change PSA: Interoperable mousedown event cancellation in iframe

Contact emailsmus...@chromium.org, fla...@chromium.org SpecificationNone Summary Make mouse event targets agnostic to mousedown event cancellation when the pointer is dragged out of an iframe. When the mouse is dragged out of an iframe, all browsers (including Chrome) send mousemove and mouseup

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

tuning the use-counter. On Thu, Dec 7, 2023 at 10:14 AM Rick Byers wrote: > > > On Wed, Dec 6, 2023 at 5:08 PM Mustaq Ahmed wrote: > >> > I assume cancelling the mousedown (but not the mousemove) still >> prevents selection and drag-and-drop in all browsers, is that right

Re: [blink-dev] Re: Web-Facing Change PSA: Interoperable mousedown event cancellation in iframe

fires when the mouse event starts within the Iframe. This prevents >>>>> the grid overlay feature from recognizing elements being dragged into it, >>>>> which breaks the drag-and-drop experience. Users can no longer effectively >>>>> place elements into specific cells of

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

Mustaq Ahmed wrote: > A quick update: our use-counter on Chrome 122 Canary/Dev came out higher > than we expected---it is suggesting that at most 0.11% page loads are > affected. > > We will expand the finch trail to 50% Beta plus 1% Stable now to get more > data, and then look int

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

e? > > On Mon, Mar 4, 2024 at 6:09 PM Mustaq Ahmed wrote: > >> UKM data shows that only a few popular sites are affecting our >> use-counters. We already confirmed that one of those sites is not broken >> at all, only showing text selection on menu items. We are

[blink-dev] Intent to Ship: Non-composed Mouse and Pointer enter/leave events

Contact emailsmus...@chromium.org Specificationhttps://w3c.github.io/uievents/#event-type-mouseenter https://w3c.github.io/pointerevents/#attributes-and-default-actions Summary Make the event.composed property in mouseenter, mouseleave, pointerenter and pointerleave events "false" to be spec com

Re: [blink-dev] Intent to Ship: Non-composed Mouse and Pointer enter/leave events

s / breaking change plan, >> right? I tend to agree the compat risk is very low and we can think of this >> just as a minor bug-fix. I don't see any easy way to measure the compat >> risk quantifiably. >> >> LGTM1 >> >> >> >> On Wed, May 24,

Re: [blink-dev] Intent to Implement and Ship: Remove Payment Request User Activation Requirement

Hi Stephen: Your summary is correct: determining how much "remaining time" to carry over a navigation is an unanswered question for user activation here but more importantly, carrying even a few milliseconds across a navigation is prone to abuse. For example, imagine accidentally clicking on an a

Re: [blink-dev] Intent to Ship: Capability Delegation with Payment Request

other intent >>> to change the behavior to require activation, after a suitable period and >>> working with sites to migrate? >>> >>> Chris >>> >>> On Thu, Jan 27, 2022 at 11:13 PM Yoav Weiss >>> wrote: >>> >>>> LGTM2 %

Re: [blink-dev] Intent to Implement and Ship: Fullscreen Capability Delegation

t written a WPT at that time. We have one under review now: https://github.com/web-platform-tests/wpt/pull/34004 Mustaq On Sun, May 8, 2022 at 11:07 PM Ajay Rahatekar wrote: > +Ajay Rahatekar > > On Monday, April 25, 2022 at 12:29:29 PM UTC-7 mike...@chromium.org wrote: > >> Hi M

[blink-dev] PSA: Simultaneous touch-drag and context-menu is getting enabled on Android 100+

On Android we are soon enabling touch-dragging following a long-press, which could subtly affect custom context-menu closing behavior in certain websites. We are not exposing any events that didn't exist before but we are changing when these events may fire on some devices/content. This can cause

[blink-dev] Re: PSA: Simultaneous touch-drag and context-menu is getting enabled on Android 100+

am trying to open context menu to say open a new tab, the drag > function is overriding my hold function and the context menu is getting > cancelled in an instant. No idea how to tackle the issue. > > On Thursday, June 16, 2022 at 5:31:09 PM UTC+1 Mustaq Ahmed wrote: > >> On A

Re: [EXTERNAL] Re: [blink-dev] Intent to Prototype: PointerEvent.deviceId for Mult-Pen Inking

be moved into the PE > spec once L3 reaches REC seems good enough to me. > > Sahir >> >> >> >> *From:* Rick Byers >> *Sent:* Tuesday, December 6, 2022 12:34 PM >> *To:* Sahir Vellani ; Mustaq Ahmed < >> mus...@chromium.org>; Robert Flack >>

Re: [blink-dev] Intent to Prototype: Capability Delegation

t; but that doesn't necessary mean that permission is delegated directly to > iframe. > > If you try to ship Capability Delegation API in above model, this would be > a bypass of permission prompt or delegating permission to cross-origin > iframes without user's knowledge. > &

[blink-dev] Re: Intent to Ship: Capability Delegation with Payment Request

Thanks Yoav, my answers to your questions are inline below. Mustaq On Wed, Jan 26, 2022 at 10:42 AM Yoav Weiss wrote: > Thanks for pushing this useful feature! > > On Tuesday, January 25, 2022 at 10:46:12 PM UTC+1 Mustaq Ahmed wrote: > >> Contact emails >> >&

Re: [blink-dev] Intent to Ship: Capability Delegation with Payment Request

Hi Mike: Appreciate your feedback. My answers are inline. Mustaq On Wed, Jan 26, 2022 at 6:03 PM Mike Taylor wrote: > Hi Mustaq, > > On 1/25/22 4:45 PM, Mustaq Ahmed wrote: > > Contact emails > > mus...@chromium.org, smcgr...@chromium.org > Explainer > > http

Re: [blink-dev] Intent to Deprecate and Remove: Calling PaymentRequest.show without user activation

I think [1] would be useful for developers but I see two blockers here: first we need to land the Capability Delegation patch in HTML spec as a "reference point" for this idea, then the PR for navigat

Re: [blink-dev] Intent to Deprecate and Remove: Calling PaymentRequest.show without user activation

On Tue, Feb 15, 2022 at 11:16 AM Chris Harrelson wrote: > LGTM2 for the extension to 102, but comments below. It would be very good > to make progress on landing additional spec pieces. > > On Tue, Feb 15, 2022 at 8:09 AM 'Mustaq Ahmed' via blink-dev < > blink-dev