SOLVED

Beta 79.0.309.51 problems with touch keyboard

%3CLINGO-SUB%20id%3D%22lingo-sub-1068361%22%20slang%3D%22en-US%22%3EBeta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068361%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20this%20version%20the%20touch%20keyboard%20is%20having%20issues.%3C%2FP%3E%3CP%3EIt%20sometimes%20works%2C%20sometimes%20it%20does%20NOT%20activate%20then%20clicking%20on%20the%20URL%20bar.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069037%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069037%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%20Thanks%20for%20letting%20us%20know!%20We%20are%20currently%20aware%20of%20one%20issue%20that%20has%20been%20affecting%20the%20older%20touch%20keyboards.%20If%20you%20have%20an%20older%20version%2C%20the%20interim%20recommendation%20is%20opting-out%2Fturning%20it%20off%20for%20now%2C%20if%20possible.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20loop%20back%20if%20you're%20either%20already%20using%20the%20newest%20keyboard%20or%20experience%20any%20other%20bugs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProject%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069385%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069385%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes-serafinski%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20yes%20it's%20the%20older%20keyboard%20on%20this%20device.%20Running%20on%201607%20LTSB%20so%20it%20doesn't%20have%20the%20newer%20keyboard.%20I%20believe%20it's%201607%20and%201703%20that%20have%20that%20keyboard%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20not%20exactly%20the%20same%20Issue%20as%20in%20dev%2Fcanary%20either.%20On%20those%20the%20failure%20rate%20was%20100%25.%20On%20beta%20it's%20maybe%2050%25%20and%20I%20haven't%20found%20a%20good%20method%20to%20provoke%20it%20either%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069826%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069826%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%3EThis%20issue%20about%20the%20virtual%20keyboard%2FSIP%20(Software%20Input%20Panel)%20not%20coming%20up%20is%20based%20on%20the%20changes%20inside%20the%20Chromium%20engine%2C%20and%20affects%20all%20chrome%20driven%20browsers%20for%20the%20Windows%20platform.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20bug%20is%20meanwhile%20fixed%20in%20Google%20Canary%20%2381.0.3999.0%20%2C%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%3C%2FA%3E%26nbsp%3Bfor%20details.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20the%20Edge%20Team%20will%20update%20to%20the%20new%20Chromium%20engine%20soon%2C%20so%20this%20will%20be%20fixed%20for%20us%20Edge%20users%2C%20too.%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20check%20the%20version%20of%20the%20Chromium%20Engine%20type%20%3CSTRONG%3Eedge%3A%2F%2Fversion%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EThen%20in%20the%20section%20%22User-Agent%22%20look%20for%20the%20entry%3A%26nbsp%3B%3CSPAN%3EChrome%2F80.x.xxx.x%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069993%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069993%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%20but%20this%20is%20not%20that%20Issue.%3C%2FP%3E%3CP%3EThis%20is%20a%20new%20one.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20old%20one%20failed%20100%25%20of%20the%20times%2C%20this%20one%20is%20sporadic.%3C%2FP%3E%3CP%3EThe%20old%20one%20started%20on%20chromium%2080%20(%3CSPAN%3E80.0.3948.0)%3C%2FSPAN%3E.%20This%20issue%20is%20on%2079%20(%3CSPAN%3E79.0.3945.79).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071076%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071076%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes-serafinski%3C%2FA%3E%26nbsp%3B%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%3EI'm%20starting%20to%20see%20some%20patterns.%3C%2FP%3E%3CP%3EI%20think%20there%20are%20three%20different%20outcomes%20when%20i%20click%20on%20the%20url%20bar.%3C%2FP%3E%3CP%3E1.%20The%20touch%20keyboard%20comes%20up%20as%20expected%3C%2FP%3E%3CP%3E2.%20The%20entire%20url%20is%20highlighted%20but%20no%20touch%20keyboard.%20In%20this%20case%20it%20often%20helps%20to%20touch%20the%20URL%20bar%20again.%20Now%20the%20keyboard%20comes%20up%3C%2FP%3E%3CP%3E3.%20no%20highlight%20but%20you%20get%20a%20cursor%20marker%20in%20the%20url%20field%20and%20no%20keyboard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20started%20my%20recording%20software%20to%20get%20a%20video%20of%20it%20-%20Now%20it%20works%20all%20the%20time%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073023%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073023%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%3BThanks%20for%20the%20additional%20details.%20I%20chatted%20with%20one%20of%20our%20devs%3B%20they%20suspect%20that%20this%20should%20be%20fixed%20across%20Chromium%20browsers%20after%20the%20next%20update%20and%20recommend%20you%20give%20it%20a%20try%20on%20subsequent%20Canary%20updates.%20But%20please%20let%20us%20know%20if%20it%20reoccurs!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProject%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073110%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073110%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20believe%20they%20are%20right.%20Chromium%20did%20fix%20a%20touch%20related%20bug%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%23c34%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1022295%23c34%3C%2FA%3E.%20With%20Chromium%20Canary%20(%3CSPAN%3E81.0.3997.0%20or%20higher)%20the%20issue%20is%20gone.%20That%20patch%20has%20also%20been%20merged%20into%20Chromium%2080.3987%20but%20there%20is%20no%20Chromium%20dev%20with%20that%20or%20a%20higher%20build%20number%20yet%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20just%20wanted%20to%20alert%20you%20of%20this%20extra%20issue%20in%2079.X%20since%20it's%20a%20lover%20series%20(80%20did%20work%20up%20to%20early%203948)%20and%20as%20I%20understand%20it%20is%20scheduled%20to%20be%20released%20in%20less%20than%20a%20month.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETo%20try%20to%20summarize%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20beta%20up%20to%20about%20two%20weeks%20ago%20was%20good%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20beta%26nbsp%3B%20309.51%20and%20forward%20has%20%22reduced%20functionality%22%20(fails%20maybe%2010-15%25%20of%20times%20-%20no%20pattern%20on%20it%20yet%20but%20believed%26nbsp%3Bto%20only%20impact%20the%20old%20keyboard)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20dev%20-%20currently%20broken%20and%20I'm%20a%20little%20worried%20since%20the%20broken%20build%20is%20supposed%20to%20be%20the%20next%20beta%20if%20I%20understand%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3Bright.%20I%20would%20like%20to%20suggest%20that%20it%20might%20be%20worth%20waiting%20a%20little%20and%20rebase%20on%2080.3948%20to%20get%20the%20keyboard%20fix%20since%20chromium%20classed%20it%20as%20a%20release%20blocker.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20Canary%20-%20Known%20broken.%20Will%20fix%20itself%20as%20soon%20as%20it%20gets%20rebased%20on%2081.3997%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELong%20post%20but%20I%20hope%20it%20was%20of%20some%20value%3C%2FP%3E%3CP%3EMerry%20Christmas%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073228%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073228%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%3BI%20can%20also%20talk%20to%20the%20team%20about%20porting%20the%20fix%20for%20that%20bug%20to%20Dev%2Fthe%20next%20Beta%2C%20but%20I'm%20not%20sure%20what%20the%20bar%20is%20for%20getting%20fixes%20in.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073607%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%20would%20be%20great%20if%20it%20could%20be%20done%20for%20all%203%20flavours%20before%20the%20holidays.%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20revised%20the%20fix%20a%20few%20days%20ago%2C%20but%20it's%20stable%20now.%20The%20final%20fixed%20Chromium%20releases%20are%3A%26nbsp%3B%3C%2FP%3E%3CP%3E81.0.3999.0%20(for%20Canary)%3C%2FP%3E%3CP%3E%3CSPAN%3E80.0.3987.19%20(for%20Dev)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E79.0.3945.96%20(for%20Beta)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20and%20Happy%20Holidays%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1082579%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1082579%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%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%3EJust%20a%20quick%20feedback.%20Latest%20Canary%20has%20the%20fixes%20and%20works%20well.%3C%2FP%3E%3CP%3EHappy%20new%20year%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1082852%22%20slang%3D%22en-US%22%3ERe%3A%20Beta%2079.0.309.51%20problems%20with%20touch%20keyboard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1082852%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%3BAwesome%2C%20glad%20to%20hear%20it!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProject%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

With this version the touch keyboard is having issues.

It sometimes works, sometimes it does NOT activate then clicking on the URL bar.

 

11 Replies
Highlighted

@matsmcp Thanks for letting us know! We are currently aware of one issue that has been affecting the older touch keyboards. If you have an older version, the interim recommendation is opting-out/turning it off for now, if possible.

 

Please loop back if you're either already using the newest keyboard or experience any other bugs.

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

Highlighted

@fawkes 

 

Hi, yes it's the older keyboard on this device. Running on 1607 LTSB so it doesn't have the newer keyboard. I believe it's 1607 and 1703 that have that keyboard 

 

It's not exactly the same Issue as in dev/canary either. On those the failure rate was 100%. On beta it's maybe 50% and I haven't found a good method to provoke it either

Highlighted

@matsmcp 

 

This issue about the virtual keyboard/SIP (Software Input Panel) not coming up is based on the changes inside the Chromium engine, and affects all chrome driven browsers for the Windows platform. 

The bug is meanwhile fixed in Google Canary #81.0.3999.0 , see https://bugs.chromium.org/p/chromium/issues/detail?id=1022295 for details. 

 

I hope the Edge Team will update to the new Chromium engine soon, so this will be fixed for us Edge users, too. 

To check the version of the Chromium Engine type edge://version

Then in the section "User-Agent" look for the entry: Chrome/80.x.xxx.x

 

Highlighted

@Neon01 

 

Sorry but this is not that Issue.

This is a new one. 

The old one failed 100% of the times, this one is sporadic.

The old one started on chromium 80 (80.0.3948.0). This issue is on 79 (79.0.3945.79).

 

Highlighted

@fawkes @Neon01 

 

I'm starting to see some patterns.

I think there are three different outcomes when i click on the url bar.

1. The touch keyboard comes up as expected

2. The entire url is highlighted but no touch keyboard. In this case it often helps to touch the URL bar again. Now the keyboard comes up

3. no highlight but you get a cursor marker in the url field and no keyboard

 

I started my recording software to get a video of it - Now it works all the time

Highlighted

@matsmcp Thanks for the additional details. I chatted with one of our devs; they suspect that this should be fixed across Chromium browsers after the next update and recommend you give it a try on subsequent Canary updates. But please let us know if it reoccurs! 

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

Highlighted

@fawkes 

 

I do believe they are right. Chromium did fix a touch related bug in https://bugs.chromium.org/p/chromium/issues/detail?id=1022295#c34. With Chromium Canary (81.0.3997.0 or higher) the issue is gone. That patch has also been merged into Chromium 80.3987 but there is no Chromium dev with that or a higher build number yet

 

I just wanted to alert you of this extra issue in 79.X since it's a lover series (80 did work up to early 3948) and as I understand it is scheduled to be released in less than a month.

 

To try to summarize 

Edge beta up to about two weeks ago was good

Edge beta  309.51 and forward has "reduced functionality" (fails maybe 10-15% of times - no pattern on it yet but believed to only impact the old keyboard)

Edge dev - currently broken and I'm a little worried since the broken build is supposed to be the next beta if I understand @josh_bodner right. I would like to suggest that it might be worth waiting a little and rebase on 80.3948 to get the keyboard fix since chromium classed it as a release blocker.

Edge Canary - Known broken. Will fix itself as soon as it gets rebased on 81.3997

 

Long post but I hope it was of some value

Merry Christmas 

Highlighted
Best Response confirmed by matsmcp (Frequent Contributor)
Solution

@matsmcp I can also talk to the team about porting the fix for that bug to Dev/the next Beta, but I'm not sure what the bar is for getting fixes in.  

Highlighted

@fawkes 

 

Hello, would be great if it could be done for all 3 flavours before the holidays. 

They revised the fix a few days ago, but it's stable now. The final fixed Chromium releases are: 

81.0.3999.0 (for Canary)

80.0.3987.19 (for Dev)

79.0.3945.96 (for Beta)

 

Thanks and Happy Holidays

 

Highlighted

@fawkes @josh_bodner @Neon01 

 

Just a quick feedback. Latest Canary has the fixes and works well.

Happy new year

Highlighted

@matsmcp Awesome, glad to hear it!

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge