menu behaviour - mouse hover vs touch taps

%3CLINGO-SUB%20id%3D%22lingo-sub-820310%22%20slang%3D%22en-US%22%3Emenu%20behaviour%20-%20mouse%20hover%20vs%20touch%20taps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-820310%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20an%20enterprise%20application%20that%20we%20have%20(Infor)%2C%20it%20has%20menus%20that%20are%20more%20designed%20with%20mouse%20pointer%20hover%20instead%20of%20touch.%26nbsp%3B%20When%20using%20touch%20to%20access%20the%20menu%20that%20designed%20to%20expand%20further%20into%20sub-menus%20(entries%20with%26nbsp%3B%20arrow%20symbols%20beside%20them)%2C%20the%20entire%20menu%20disappears.%26nbsp%3B%20When%20you%20touch%20it%20again%2C%20the%20sub-menu%20will%20show%20up%20in%20its%20place.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20this%20behaviour%20occurs%20on%20all%20current%20touch-based%20devices%20that%20I%20have%20used%2C%20with%20various%20different%20browsers%20(iOS%2012%20with%20Safari%2C%20Windows%2010%20touchscreen%20laptop%20with%20Chrome%2C%20Edge%20classic%2C%20and%20Edge%20Chromium%20Beta%2C%20as%20well%20as%20Android%20tablets%20with%20Chrome%20browser).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20when%20I%20tested%20an%20iPad%20running%20iPadOS%2013%20beta%20(public%20beta%207)%2C%20this%20behaviour%20has%20been%20changed%20for%20the%20better.%26nbsp%3B%20Instead%20of%20collapsing%20the%20entire%20menu%20when%20a%20sub-menu%20is%20tapped%2C%20Safari%20in%20iOS%2013%20beta%20will%20make%20menu%20appears%20on%20the%20side%2C%20which%20is%20similar%20to%20the%20user%20experience%20when%20using%20mouse.%26nbsp%3B%20This%20alone%20makes%20using%20this%20enterprise%20application%20that%20we%20have%20much%20more%20user%20friendly%20on%20touchscreen%20devices%2C%20which%20could%20greatly%20improve%20the%20usability%20of%20our%20field%20workers.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20know%20if%20the%20team%20here%20can%20make%20an%20enhancement%20request%20to%20future%20releases%20of%20Edge%20to%20change%20the%20behaviour%20of%20hover%20menu%20to%20act%20similar%20to%20iPadOS%2013.%26nbsp%3B%20(Maybe%20you%20can%20upstream%20that%20change%20to%20Chromium%20itself%20so%20that%20all%20Chromium-based%20browsers%20can%20benefit.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20included%20two%20screen%20captures%3A%26nbsp%3B%20first%20one%20the%20the%20behaviour%20of%20Windows%20with%20Chrome%2FEdge%20(both%20Classic%20and%20Chromium)%2C%20iOS%2012%20Safari%20and%20Android%20tablets%20with%20Chrome%2C%20while%20the%20second%20one%20is%20the%20behaviour%20of%20iPadOS%2013%20Safari.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20800px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F128222i0528B4B69F38A9DC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Infor_others.gif%22%20title%3D%22Infor_others.gif%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3Ehover%20menu%20-%20iOS%2012%20and%20Windows%2010%20Edge%20classic%2FEdge%20Chromium%2FChrome%20behaviour%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20800px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F128223i555D947271BFAFE1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Infor_ios13.gif%22%20title%3D%22Infor_ios13.gif%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3Ehover%20menu%20-%20iPadOS%2013%20Safari%20behaviour%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-820310%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehover%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-827751%22%20slang%3D%22en-US%22%3ERe%3A%20menu%20behaviour%20-%20mouse%20hover%20vs%20touch%20taps%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-827751%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F397434%22%20target%3D%22_blank%22%3E%404tran%3C%2FA%3E%2C%20I%20am%20not%20sure%20what%20we%20can%20do%20here%2C%20but%20we%20are%20investing%20in%20accessibility%20and%20touch%20improvements%20in%20the%20Chromium%20tree.%26nbsp%3B%20I%20will%20forward%20this%20thread%20on%20to%20the%20owner%20of%20these%20areas%20and%20see%20what%20they%20say.%26nbsp%3B%20Thanks%20-%20Elliot%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

In an enterprise application that we have (Infor), it has menus that are more designed with mouse pointer hover instead of touch.  When using touch to access the menu that designed to expand further into sub-menus (entries with  arrow symbols beside them), the entire menu disappears.  When you touch it again, the sub-menu will show up in its place. 

 

So far this behaviour occurs on all current touch-based devices that I have used, with various different browsers (iOS 12 with Safari, Windows 10 touchscreen laptop with Chrome, Edge classic, and Edge Chromium Beta, as well as Android tablets with Chrome browser).

 

However, when I tested an iPad running iPadOS 13 beta (public beta 7), this behaviour has been changed for the better.  Instead of collapsing the entire menu when a sub-menu is tapped, Safari in iOS 13 beta will make menu appears on the side, which is similar to the user experience when using mouse.  This alone makes using this enterprise application that we have much more user friendly on touchscreen devices, which could greatly improve the usability of our field workers. 

 

I would like to know if the team here can make an enhancement request to future releases of Edge to change the behaviour of hover menu to act similar to iPadOS 13.  (Maybe you can upstream that change to Chromium itself so that all Chromium-based browsers can benefit.)

 

I have included two screen captures:  first one the the behaviour of Windows with Chrome/Edge (both Classic and Chromium), iOS 12 Safari and Android tablets with Chrome, while the second one is the behaviour of iPadOS 13 Safari.

 

hover menu - iOS 12 and Windows 10 Edge classic/Edge Chromium/Chrome behaviourhover menu - iOS 12 and Windows 10 Edge classic/Edge Chromium/Chrome behaviour

hover menu - iPadOS 13 Safari behaviourhover menu - iPadOS 13 Safari behaviour

1 Reply
Highlighted

Hi @4tran, I am not sure what we can do here, but we are investing in accessibility and touch improvements in the Chromium tree.  I will forward this thread on to the owner of these areas and see what they say.  Thanks - Elliot