Is someone working on this?

Rick, could you triage? Is this intentional or no?

Ah, sorry for this change in behavior. Chrome has never intentionally opened a context menu for mouse-click-and-hold. But in earlier versions of Chrome for Android a mouse device was treated by the operating system and hence Chrome mostly like a touchscreen, which would have led to the behavior you describe. At some point we added property mouse support to Chrome for Android so that mice and touchscreens on Chrome, ChromeOS and Windows all behaved exactly the same. I don't think we want to go back on that decision, there are more and more scenarios these days with a physical mouse connected to an android device is expected to behave just like a mouse does on any other platform.

However, perhaps there's an easy accessibility option we could add to enable this? I.e. treat-mouse-as-touch.  +Navid who leads input, and assigning back to Dominic to consider as an accessibility feature request.

s/property mouse support/proper mouse support/

Context  bug 468806 , https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/mouse$20touch$20android%7Csort:date/blink-dev/cNaFvMaYtNA/wRcSsj0jAwAJ

Can we detect if a mouse is present? It'd be nice to only expose the "Treat mouse as touch" setting if there's a mouse present, that way it wouldn't clutter the UI for most users.

dmazzoni@: In Chrome Android, we can detect mouse presence dynamically through a WebPreference field:
https://cs.chromium.org/chromium/src/third_party/blink/public/platform/pointer_properties.h?rcl=328bff933a0867acb134a38291357ebb9724b21f&l=11

We started an internal discussion last year on mouse accessibility.  I will revive the thread.

Thank you for your efforts!

I would like to follow the discussion about mouse accessibility and give my input. Is there a link to the appropriate thread?

Here is a short input, how I use the mouse:

I am physically disabled and have a neuromuscular disease. Therefore, with radius of movement is very limited, especially my hands I can not use, so input via touch is not possible for me. Even a normal mouse is not usable for me. Instead, I use an assistive technology. My wheelchair has a Bluetooth mouse module. I can control this via the joystick of the wheelchair to move the mouse arrow. In addition, I can perform jerky, fast movements of the joystick in the four orthogonal directions (top, bottom, right and left) mouse actions: fast move the joystick forward (above) Lust left mouse click, left scrolls with the mouse wheel up, right scrolls down. The move backwards (down) is not occupied for me, because I can not do this fast. In principle, I can only "point 'n' click" on each individual points swipes, complex mouse gestures or drag and drop are not possible for me.

I also advise on barrier-free website development (I am a web developer myself) and always advise to make as few assumptions as possible about the users' abilities. Ie. one should avoid mouse gestures etc. as the sole input option and always offer a fallback. Of course, the same applies to the UI design.

The simplest input principle that you should always assume is a basic point 'n' click. This is always possible and is supported by any AT that simulates the mouse. You should not go out of further assumptions, especially not that, for example, a right mouse button is present or the mouse wheel (even if I can use it in my personal case).

Completely agreed that good website or app design should not assume the user can do anything other than click!!!

It sounds like the best solution would be a setting that lets you treat mouse input as touch input. That would give you the old behavior without breaking anyone who wants to use both touch and mouse together.

Changing this to an open feature request.

I also filed an Android bug, they may want to address this at a system level:
b/120911786

Thank you! However, it's not a (simple) feature request, but rather a regression ;-)