The Android team is apparently seeing reports like yours. Please comment on this bug <https://crbug.com/1340584> about your experience.
On Wed, Jun 29, 2022 at 4:22 AM Creature Feature <[email protected]> wrote: > Hello, I have recently became aware of this and I am having a slight issue > - when I 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 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 two changes in observable behavior in Chrome for Android: >> >> - >> >> Elements with a draggable >> <https://html.spec.whatwg.org/multipage/dnd.html#the-draggable-attribute> >> attribute would start responding to touch-drag interaction. >> - >> >> Custom context-menu may co-exist with an ongoing drag. >> >> Draggable elements >> >> On mobile we never supported drag-and-drop >> <https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event#browser_compatibility>, >> so draggable elements (like those in this >> <https://simple-drag-and-drop-1.glitch.me/> demo) never really responded >> to touch-drags. More precisely, we fired neither drag nor dragend >> events after a dragstart event, and in many cases we couldn’t fire even >> a dragstart event because a long-press would invoke a modal context menu >> which blocks all events from the page behind. >> >> This upcoming change would expose correct firing of dragstart, drag and >> dragend events to the page, and any draggable element would start >> responding. >> Custom context menus >> >> The upcoming change would possibly provide an awkward experience on sites >> that draw a custom context-menu. Certain types of target elements would >> now receive both dragstart and contextmenu events, so some of these >> sites would continue to show a custom context-menu while a drag-and-drop is >> ongoing. But any reasonable custom context-menu is expected to close on a >> tap outside the menu, and that would be an easy and intuitive “fix” for the >> user. So in the end, this would feel like a bad UI experience instead of a >> broken site. >> Future plans >> >> Longer term, we are proposing to enhance custom context-menu support in >> the Web platform through a new event: >> >> - >> >> Github discussion: https://github.com/w3c/uievents/issues/309 >> - >> >> Integration with popup: https://github.com/openui/open-ui/issues/426 >> - >> >> Chrome bug: https://crbug.com/1243718 >> >> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB0cuO5HGpVyHYBKHXHCa9VnhcmyZ2GuBjrK7ov1DTQWXdFNVQ%40mail.gmail.com.
