Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
1–10 of 23 posts
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#2Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#3Personally, I think this could just be chalked up to UA string parsing issues. Not worth the trouble for Google to kick up a storm over a marginal market share browser.
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#4Unsupported browser is a bit of a joke anyways in times of modern web standards...
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#5Personally, I think this could just be chalked up to UA string parsing issues. Not worth the trouble for Google to kick up a storm over a marginal market share browser.
Certain commenters suggested that the exact partial UA string identifying Edge was blacklisted. I'd love to see a more detailed analysis.
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#6Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#7Earlier quoted context omitted.
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"...
[0] https://www.bleepingcomputer.com/news/microsoft/the-new-micr...
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#8But how do you support a browser that hasn't been released yet? Give them some time.
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#9But how do you support a browser that hasn't been released yet? Give them some time.
https://en.wikipedia.org/wiki/Feature_detection_(web_develop...
Re: Google has added “unsupported browser” warnings for Edge Chromium on Google Docs
#10Personally, I think this could just be chalked up to UA string parsing issues. Not worth the trouble for Google to kick up a storm over a marginal market share browser.
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...