Multiple issues with touch input in Edge

%3CLINGO-SUB%20id%3D%22lingo-sub-1266317%22%20slang%3D%22en-US%22%3EMultiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1266317%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20numerous%20issues%20with%20using%20Edge%20browser%20by%20touch.%20In%20annoyance%20from%20biggest%20to%20smallest%3A%3C%2FP%3E%3COL%3E%3CLI%3EOn%20YouTube%20subscriptions%20and%20recommended%20pages%20tap%26amp%3Bhold%20on%20the%20video%20doesn't%20produce%20the%20context%20menu%20to%20open%20it%20in%20a%20new%20tab%20but%20instead%20starts%20the%20video.%3C%2FLI%3E%3CLI%3EThe%20text%20selection%20ui%2Fux%20is%20different%20from%20the%20rest%20of%20the%20OS.%20That%20means%20in%20all%20of%20Windows%20one%20would%20tap%20or%20doubletap%20the%20text%20to%20select%20it%2C%20yet%20in%20Edge%20one%20has%20to%20tap%26amp%3Bhold.%20That%20messes%20up%20the%20muscle%20memory%20and%20I%20still%20try%20to%20tap%20or%20double%20tap%20in%20edge%20and%20then%20in%2C%20say%2C%20Twitter%20I%20try%20to%20%3Ftap%26amp%3Bhold...%3C%2FLI%3E%3CLI%3ETap%26amp%3Bhold%20for%20text%20selection%20in%20edge%20often%20doesn't%20open%20the%20scroll%20thingies%20to%20select%20more%20text%20and%20the%20copy%20button%2C%20someone%20has%20to%20use%20touch%20keyboard%20shortcuts%3C%2FLI%3E%3CLI%3ETouch%20keyboard%20shortcuts%20have%20a%20huge%20lag%20between%20pressing%20ctrl%20and%20c%2Fv%2Fa%20to%20produce%20the%20actual%20shortcut%20command.%20Instead%2C%20if%20you%20don't%20wait%20like%2010%20seconds%2C%20it%20just%20produces%20the%20letter.%3C%2FLI%3E%3CLI%3EFast%20and%20frequent%20touch%20input%20(tapping%20many%20time%20fast%20in%20a%20small%20area)%20freezes%20the%20rest%20of%20touch%20input%20on%20that%20tab%20or%20on%20all%20open%20tabs%20and%20one%20has%20to%20restart%20the%20browser%20for%20it%20to%20work%20again%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1270450%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1270450%22%20slang%3D%22en-US%22%3E%3CP%3EUuu%2C%20theres%20another%20one!%20Trying%20to%20drag%20a%20tab%20so%20it%20becomes%20a%20new%20window%20with%20touch%20also%20doesn't%20work...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271866%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271866%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F518809%22%20target%3D%22_blank%22%3E%40Mustakivi%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20mentioning%20this.%3C%2FP%3E%3CP%3EYes%2C%20the%20lack%20of%20touch%20optimization%20is%20driving%20me%20crazy%20too%20since%20day%20one%20of%20edge%20chromium.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20text%20selection%20is%20uncommon%20(tap%20and%20hold%2C%20you%20mentioned%20it)%20and%20extremely%20unstable.%20I%20often%20can't%20select%20anything%20anymore%20or%20the%20whole%20page%20freezes%20when%20working%20with%20text%20selection%2C%20especially%20when%20the%20page%20is%20accidentially%20zoomed%20a%20bit%2C%20which%20happens%20quite%20often%20to%20me.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20annoying%20thing%20is%20that%20on%20larger%20text%20inputs%20the%20whole%20inputsection%20doesn't%20move%20up%20when%20you%20click%20into%20a%20lower%20section%2C%20so%20the%20cursor%20is%20halfway%20or%20completely%20hidden%20by%20the%20virtual%20keyboard%20and%20you%20have%20to%20scroll%20manually%20to%20be%20able%20to%20see%20what%20you're%20typing.%20But%20that%20seems%20to%20be%20a%20general%20problem%20of%20the%20chrome%20engine%20since%20they%20changed%20the%20input%20method%20in%20october%20last%20year.%20I%20faced%20this%20on%20Googles%20Chrome%20browser%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20the%20third%20is%20the%20unstable%2C%20most%20of%20the%20time%20not%20working%20fullscreen%20dropdown%20of%20the%20tab-%20and%20addressbar.%20It%20freezes%20the%20whole%20browser%20almost%20every%20time%20I%20click%20on%20a%20tab%20after%20swiping%20it%20in.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20MS%2C%20take%20a%20look%20at%20the%20issues%20mentioned%20in%20this%20thread%2C%20they%20are%20blocking%20thousands%20and%20thousands%20of%20tablet%2Ftouchscreen%20users%20to%20switch%20to%20edge%2C%20thanks.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271881%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271881%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F518809%22%20target%3D%22_blank%22%3E%40Mustakivi%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EUuu%2C%20theres%20another%20one!%20Trying%20to%20drag%20a%20tab%20so%20it%20becomes%20a%20new%20window%20with%20touch%20also%20doesn't%20work...%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EInteresting%2C%20because%20this%20works%20for%20me%20with%20touch%2C%20both%20on%20Dev%20and%20Canary.%3CBR%20%2F%3EWhich%20version%2Fchannel%20are%20you%20on%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272160%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272160%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F382315%22%20target%3D%22_blank%22%3E%40Neon01%3C%2FA%3E%26nbsp%3Bi'm%20not%20sure%20what%20the%20lingo%20is%2C%20the%20stable%20release%20I%20guess%2C%20the%20one%20that%20replaces%20the%20old%20edge.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272184%22%20slang%3D%22en-US%22%3ERe%3A%20Multiple%20issues%20with%20touch%20input%20in%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272184%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F382315%22%20target%3D%22_blank%22%3E%40Neon01%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EPlease%20MS%2C%20take%20a%20look%20at%20the%20issues%20mentioned%20in%20this%20thread%2C%20they%20are%20blocking%20thousands%20and%20thousands%20of%20tablet%2Ftouchscreen%20users%20to%20switch%20to%20edge%2C%20thanks.%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EEverything%20in%20my%20original%20post%20applies%20to%20Chrome%2C%20Mozilla%20and%2C%20I%20assume%2C%20all%20the%20other%20chromium%20based%20browsers.%20So%20the%20issue%20here%20is%20much%20larger%20than%20people%20not%20switching%20to%20Edge.%20People%20can't%20do%20what%20they%20are%20used%20to%20doing%20on%20Windows%20using%20touch%20full%20stop.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

There are numerous issues with using Edge browser by touch. In annoyance from biggest to smallest:

  1. On YouTube subscriptions and recommended pages tap&hold on the video doesn't produce the context menu to open it in a new tab but instead starts the video.
  2. The text selection ui/ux is different from the rest of the OS. That means in all of Windows one would tap or doubletap the text to select it, yet in Edge one has to tap&hold. That messes up the muscle memory and I still try to tap or double tap in edge and then in, say, Twitter I try to ?tap&hold...
  3. Tap&hold for text selection in edge often doesn't open the scroll thingies to select more text and the copy button, someone has to use touch keyboard shortcuts
  4. Touch keyboard shortcuts have a huge lag between pressing ctrl and c/v/a to produce the actual shortcut command. Instead, if you don't wait like 10 seconds, it just produces the letter.
  5. Fast and frequent touch input (tapping many time fast in a small area) freezes the rest of touch input on that tab or on all open tabs and one has to restart the browser for it to work again
5 Replies
Highlighted

Uuu, theres another one! Trying to drag a tab so it becomes a new window with touch also doesn't work...

Highlighted

@Mustakivi 

Thanks for mentioning this.

Yes, the lack of touch optimization is driving me crazy too since day one of edge chromium. 

 

The text selection is uncommon (tap and hold, you mentioned it) and extremely unstable. I often can't select anything anymore or the whole page freezes when working with text selection, especially when the page is accidentially zoomed a bit, which happens quite often to me. 

 

Another annoying thing is that on larger text inputs the whole inputsection doesn't move up when you click into a lower section, so the cursor is halfway or completely hidden by the virtual keyboard and you have to scroll manually to be able to see what you're typing. But that seems to be a general problem of the chrome engine since they changed the input method in october last year. I faced this on Googles Chrome browser too.

 

And the third is the unstable, most of the time not working fullscreen dropdown of the tab- and addressbar. It freezes the whole browser almost every time I click on a tab after swiping it in. 

 

Please MS, take a look at the issues mentioned in this thread, they are blocking thousands and thousands of tablet/touchscreen users to switch to edge, thanks. 

 

 

 

Highlighted

@Mustakivi wrote:

Uuu, theres another one! Trying to drag a tab so it becomes a new window with touch also doesn't work...


Interesting, because this works for me with touch, both on Dev and Canary.
Which version/channel are you on?

Highlighted

@Neon01 i'm not sure what the lingo is, the stable release I guess, the one that replaces the old edge.

Highlighted

@Neon01 wrote:

Please MS, take a look at the issues mentioned in this thread, they are blocking thousands and thousands of tablet/touchscreen users to switch to edge, thanks. 


Everything in my original post applies to Chrome, Mozilla and, I assume, all the other chromium based browsers. So the issue here is much larger than people not switching to Edge. People can't do what they are used to doing on Windows using touch full stop.