SOLVED
Home

Compatibility issue with google drive

%3CLINGO-SUB%20id%3D%22lingo-sub-692400%22%20slang%3D%22en-US%22%3ECompatibility%20issue%20with%20google%20drive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692400%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20go%20to%20my%20google%20drive%20I%20get%20the%20warning%20%22You%20are%20using%20an%20unsupported%20browser.%20If%20you%20see%20some%20unexpected%20behavior%2C%20you%20may%20want%20to%20use%20a%20supported%20browser%20instead.%22%3C%2FP%3E%3CP%3EI%20have%20to%20say%20that%2C%20using%20Edge%20dev%20(76.0.182.6)%20to%20work%20with%20documents%20in%20my%26nbsp%3B%3CSPAN%3Egoogle%20drive%3C%2FSPAN%3E%3CSPAN%3E%2C%20there%20is%20no%20%22unexpected%20behavior%22%20so%20far.%20I%20do%2C%20however%2C%20expect%20from%20the%20Edge%20dev%20team%20to%20step%20forward%20in%20a%20deeper%20collaboration%26nbsp%3Bwith%26nbsp%3BGoogle%26nbsp%3Band%20eliminate%20any%20kind%20of%20incompatibilities.%26nbsp%3BBesides%2C%20this%20was%20the%20primary%20reason%20that%20Microsoft%20adopted%20chromium%3A%20%22%3CA%20title%3D%22GitHub%20article%22%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftEdge%2FMSEdge%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Edge%20and%20Chromium%20Open%20Source%3A%20Our%20Intent%3C%2FA%3E%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693873%22%20slang%3D%22en-US%22%3ERe%3A%20Compatibility%20issue%20with%20google%20drive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693873%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F360300%22%20target%3D%22_blank%22%3E%40geotso%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20something%20we%20have%20been%20working%20hard%20on%20for%20a%20while%20now.%20Google%20says%20because%20of%20code%3C%2FP%3E%0A%3CP%3Echanges%20a%20while%20ago%2C%20it%20accidentally%20caused%20issues%20with%20the%20new%20Microsoft%20Edge%20browsers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20of%20the%20Google%20code%20change%20problems%20have%20been%20fixed%20or%20workarounds%20were%20suggested.%3C%2FP%3E%0A%3CP%3EThis%20should%20be%20no%20different%20but%20so%20far%20all%20the%20features%20seem%20to%20still%20work%20fine%20with%20Google.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20feedback%2C%3C%2FP%3E%0A%3CP%3EFrank%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693880%22%20slang%3D%22en-US%22%3ERe%3A%20Compatibility%20issue%20with%20google%20drive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693880%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20able%20to%20access%20my%20Google%20Drive%2C%20but%20I%20do%20have%20an%20outdated%20version%20of%20the%20sign%20in%20screen.%20This%20does%20not%20affect%20functionality%2C%20but%20I%20don't%20like%20seeing%20the%20old%20sign%20in%20screen.%3C%2FP%3E%3CP%3EHere%20are%20screenshots%20of%20Edge%20C%20and%20%22old%22%20Edge%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Old%22%20Edge%20(up%20to%20date%20sign%20in%20screen)%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20852px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118174iCF4935C521BBC392%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Gdrive2.PNG%22%20title%3D%22Gdrive2.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EEdge%20C%20(out%20of%20date%20sign%20in%20screen)%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118175iFD349C29CB8EB988%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Gdrive.PNG%22%20title%3D%22Gdrive.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
geotso
Occasional Visitor

When I go to my google drive I get the warning "You are using an unsupported browser. If you see some unexpected behavior, you may want to use a supported browser instead."

I have to say that, using Edge dev (76.0.182.6) to work with documents in my google drive, there is no "unexpected behavior" so far. I do, however, expect from the Edge dev team to step forward in a deeper collaboration with Google and eliminate any kind of incompatibilities. Besides, this was the primary reason that Microsoft adopted chromium: "Microsoft Edge and Chromium Open Source: Our Intent".

 

Thank you

2 Replies
Solution

@geotso 

 

This is something we have been working hard on for a while now. Google says because of code

changes a while ago, it accidentally caused issues with the new Microsoft Edge browsers.

 

Most of the Google code change problems have been fixed or workarounds were suggested.

This should be no different but so far all the features seem to still work fine with Google.

 

Thanks for your feedback,

Frank

 

 

 

 

 

I am able to access my Google Drive, but I do have an outdated version of the sign in screen. This does not affect functionality, but I don't like seeing the old sign in screen.

Here are screenshots of Edge C and "old" Edge:

 

"Old" Edge (up to date sign in screen):

Gdrive2.PNG

Edge C (out of date sign in screen):

Gdrive.PNG

Related Conversations