issue with touchscreen behavior with links

%3CLINGO-SUB%20id%3D%22lingo-sub-1261842%22%20slang%3D%22en-US%22%3Eissue%20with%20touchscreen%20behavior%20with%20links%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1261842%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20filed%20it%20on%20the%20Chromium%20bug%20tracker%20(it's%20not%20specific%20to%20Edge)%20but%20thought%20I%20should%20post%20it%20here%20so%20Edge%20team%20can%20see%20it%20because%20it's%20relevant%20to%20Windows%20tablets%20and%20it's%20very%20annoying%2C%20also%2C%20maybe%20Edge%20team%20is%20more%20familiar%20with%20this%20issue%20than%20Google%20%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1065676%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1065676%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1261914%22%20slang%3D%22en-US%22%3ERe%3A%20issue%20with%20touchscreen%20behavior%20with%20links%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1261914%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318719%22%20target%3D%22_blank%22%3E%40Bdsrev%3C%2FA%3E%26nbsp%3BI%20read%20your%20chromium%20report.%20In%20legacy%20edge%2C%20a%20box%20appears%20that%20indicates%20that%20when%20you%20release%2C%20it%20will%20open%20the%20options.%20You%20can%20replicate%20this%20on%20the%20desktop%20screen%2C%20because%20edge%20was%20using%20the%20same%20tech%20as%20windows.%26nbsp%3BInterestingly%20enough%2C%20this%20also%20appears%20in%20Firefox%2C%20though%20I'm%20not%20completely%20surprised%20as%20Firefox%20has%20derived%20many%20of%20its%20feature%20ideas%20from%20edge.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22cjc2112_0-1585453419467.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180216iCD80507DC1FAD7C3%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22cjc2112_0-1585453419467.png%22%20alt%3D%22cjc2112_0-1585453419467.png%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20probably%20a%20windows%20specific%20action%20that%20is%20built%20into%20the%20underlying%20UI%20that%20is%20different%20than%20apple%2Fandroid.%20My%20suggestion%20would%20be%20for%20chromium%20to%20follow%20in%20Firefoxes%20footsteps%20because%20I%20doubt%20that%20it%20will%20be%20easy%20to%20make%20the%20mobile%20actions%20happen%20on%20windows%2C%20which%20has%20since%20quit%20developing%20the%20mobile%20parts%20of%20the%20OS.%20I%20may%20be%20wrong%20though.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20They%20may%20not%20have%20allowed%20the%20menu%20to%20popup%20because%20if%20someone%20is%20scrolling%20but%20holds%20it%20down%20too%20long%2C%20it%20would%20be%20annoying%20for%20them%20to%20tap%20away%20from%20it%20and%20continue%20to%20scroll%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262739%22%20slang%3D%22en-US%22%3ERe%3A%20issue%20with%20touchscreen%20behavior%20with%20links%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262739%22%20slang%3D%22en-US%22%3EWe'll%20see%20what%20Edge%20team%20says.%20I%20just%20tried%20it%20on%20a%20friends%20iPad%20and%20it%20behaves%20just%20like%20Android%20too%2C%20so%20maybe%20they'll%20think%20about%20changing%20this%20if%20it's%20not%20too%20much%20work.%20It's%20important%20to%20not%20allow%20all%20these%20papercuts%20to%20build%20up%20over%20time%20(%22death%20by%20a%20thousand%20papercuts%22)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1481591%22%20slang%3D%22en-US%22%3ERe%3A%20issue%20with%20touchscreen%20behavior%20with%20links%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1481591%22%20slang%3D%22en-US%22%3EI'm%20sorry%20to%20come%20back%20to%20this%20but%20I%20actually%20use%20my%20Surface%20pro%20as%20a%20tablet%20and%20this%20is%20surprisingly%20annoying%2C%20can%20someone%20please%20take%20a%20look%20at%20this%3F%20I%20just%20can't%20get%20used%20to%20it%2C%20it%20should%20work%20the%20same%20as%20Android%2FiOS%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Just filed it on the Chromium bug tracker (it's not specific to Edge) but thought I should post it here so Edge team can see it because it's relevant to Windows tablets and it's very annoying, also, maybe Edge team is more familiar with this issue than Google https://bugs.chromium.org/p/chromium/issues/detail?id=1065676

3 Replies
Highlighted

@Bdsrev I read your chromium report. In legacy edge, a box appears that indicates that when you release, it will open the options. You can replicate this on the desktop screen, because edge was using the same tech as windows. Interestingly enough, this also appears in Firefox, though I'm not completely surprised as Firefox has derived many of its feature ideas from edge.

cjc2112_0-1585453419467.png 

This is probably a windows specific action that is built into the underlying UI that is different than apple/android. My suggestion would be for chromium to follow in Firefoxes footsteps because I doubt that it will be easy to make the mobile actions happen on windows, which has since quit developing the mobile parts of the OS. I may be wrong though.

 

Edit: They may not have allowed the menu to popup because if someone is scrolling but holds it down too long, it would be annoying for them to tap away from it and continue to scroll again.

Highlighted
We'll see what Edge team says. I just tried it on a friends iPad and it behaves just like Android too, so maybe they'll think about changing this if it's not too much work. It's important to not allow all these papercuts to build up over time ("death by a thousand papercuts")
Highlighted
I'm sorry to come back to this but I actually use my Surface pro as a tablet and this is surprisingly annoying, can someone please take a look at this? I just can't get used to it, it should work the same as Android/iOS