But the bigger point is why are they even sniffing UA strings?

Google, who advocates for everybody else that you should use standards and proper feature detection, still relies on UA whitelists for their own products.

Then look at google.com homepage itself... not responsive, not in any way modern... many of their own sites perform terribly by their own guidance to other devs.

Google's hypocrisy is sickening and I'm tired of their "we own the web, do what we say" attitude.

This is why the UA contains "Edg/" not "Edge" to prevent issues like this.

It could just be there is a whitelist for Google Docs, like on Google Meet:

https://www.theverge.com/2019/4/26/18518346/google-meet-micr...

Certain commenters suggested that the exact partial UA string identifying Edge was blacklisted. I'd love to see a more detailed analysis.

I mean UA strings are such a mess. I can't even imagine what it must be for a browser called "edge chromium"...

It depends on the website [0]. Which I guess means that Microsoft is going to add Google Docs to list of special cases where they need to pretend to be a different browser.

[0] https://www.bleepingcomputer.com/news/microsoft/the-new-micr...