The non working touch keyboard

%3CLINGO-SUB%20id%3D%22lingo-sub-1065998%22%20slang%3D%22en-US%22%3EThe%20non%20working%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1065998%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20the%20beginning%20of%20November%20the%20touch%20keyboard%20is%20broken%20in%20canary%20and%20dev.%3C%2FP%3E%3CP%3EThis%20has%20been%20reported%20on%20this%20forum%20and%20also%20demonstrated%20for%20members%20of%20the%20Edge%20team%20onsite%20at%20Ignite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%20it%20has%20not%20been%20fixed%20or%20even%20added%20to%20the%20public%20known%20bugs%20list.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20make%20it%20clearer%20I%20have%20recorded%20two%20small%20videos%20of%20it.%3C%2FP%3E%3CP%3ECanary%20is%26nbsp%3B%3CSPAN%3E81.0.363.0%20and%20as%20you%20can%20see%20-%20clicking%20on%20the%20url%20bar%20does%26nbsp%3B%3CSTRONG%3ENOT%3C%2FSTRONG%3E%20bring%20up%20the%20touch%20keyboard%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EBeta%20is%26nbsp%3B79.0.309.47%20and%20it%26nbsp%3Bdoes%20bring%20up%20the%20keyboard%20as%20it%20should%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOn%20a%20Surface%20this%20is%20a%20major%20usability%20issue%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1067105%22%20slang%3D%22en-US%22%3ERe%3A%20The%20non%20working%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1067105%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%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%2C%20I'm%20only%20got%20a%201607%20LTSB%20install%20on%20a%20sp4%20currently%20and%20it%20doesn't%20have%20that%20regvalue.%3C%2FP%3E%3CP%3EThe%20Chromium%20patch%20do%20work%20on%20that%20though.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20like%20it%20was%20a%20MS%20Employee%20that%20fixed%20it%20too.%3C%2FP%3E%3CP%3EThanks%20to%20you%20for%20making%20the%20Surface%20usable%20again%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20we%20only%20have%20to%20wait%20to%20get%20it%20in%20canary%20and%20dev%20too%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1066935%22%20slang%3D%22en-US%22%3ERe%3A%20The%20non%20working%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1066935%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F375670%22%20target%3D%22_blank%22%3E%40matsmcp%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20seems%20the%20guy%20from%20the%20Google%20Chromium%20Team%20finally%20fixed%20it%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20now%20live%20for%20testing%20on%20the%20latest%20Google%20Canary%20%2381.0.3997.0%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20Edge%20Canary%20will%20update%20to%20the%20new%20chromium%20core%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBtw.%20I%20see%20from%20your%20screencast%20that%20you're%20too%20using%20the%20old%2Flegacy%20keyboard%20(registry-key%3A%20%22DisableNewKeyboardExperience%22).%20With%20the%20fix%20the%20virtual%20keyboard%20now%20properly%20invokes%20on%20textfields%20in%20lastest%20Google%20Canary%2C%20but%20doesn't%20close%20when%20leaving%20or%20touching%20on%20an%20empty%20space.%3C%2FP%3E%3CP%3EBut%20with%20the%20new%20virtual%20keybord%20it%20works.%20Can%20you%20please%20test%20and%20confirm%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Since the beginning of November the touch keyboard is broken in canary and dev.

This has been reported on this forum and also demonstrated for members of the Edge team onsite at Ignite.

 

So far it has not been fixed or even added to the public known bugs list.

 

To make it clearer I have recorded two small videos of it.

Canary is 81.0.363.0 and as you can see - clicking on the url bar does NOT bring up the touch keyboard

Beta is 79.0.309.47 and it does bring up the keyboard as it should

 

On a Surface this is a major usability issue

2 Replies
Highlighted

@matsmcp 

 

Hi, seems the guy from the Google Chromium Team finally fixed it: 

https://bugs.chromium.org/p/chromium/issues/detail?id=1022295 

 

It's now live for testing on the latest Google Canary #81.0.3997.0 

Hope Edge Canary will update to the new chromium core soon.

 

Btw. I see from your screencast that you're too using the old/legacy keyboard (registry-key: "DisableNewKeyboardExperience"). With the fix the virtual keyboard now properly invokes on textfields in lastest Google Canary, but doesn't close when leaving or touching on an empty space.

But with the new virtual keybord it works. Can you please test and confirm?

 

Thanks

Highlighted

@Neon01 

 

Sorry, I'm only got a 1607 LTSB install on a sp4 currently and it doesn't have that regvalue.

The Chromium patch do work on that though.

 

Seems like it was a MS Employee that fixed it too.

Thanks to you for making the Surface usable again

 

Now we only have to wait to get it in canary and dev too