1894308 - docs.dingtalk.com hits a browser-not-supported page in Firefox

Status: NEW

(Web Compatibility :: Site Reports, defect, P3)

Description

[Daniel Holbert [:dholbert]]

We got a site breakage report.

Here's a URI that reproduces the issue (slightly adjusted to remove the specific doc identifier):
https://alidocs.dingtalk.com/not-supported-env?goto=https%3A%2F%2Fdocs.dingtalk.com

In Firefox, that URI loads a page that says:

This type of browser is not supported, the document cannot be opened
It is recommended to use the latest version of the recommended browser to open

In other browsers[1], that page redirects to the goto= reference (which in this case is https://docs.dingtalk.com/ )

(Presumably the user who reported the issue was actually starting with another URL, and dingtalk redirected them to this not-supported-env page, but this URL seems to be fine to directly reproduce the issue regardless.)

[1] Other browsers that I tested that redirect just fine
Chrome 126dev on Linux
Edge 124 on Windows 11
Safari 17.3 on macOS

Comment 1

[Daniel Holbert [:dholbert]]

I haven't clicked through to see if the site actually works in Firefox or not, e.g. with a UA override spoof.

The site is mostly in Chinese, and it seems to require a username/login to actually view a doc, I think, so there's some setup required to really investigate here.

Comment 2

[Daniel Holbert [:dholbert]]

Attachment: screenshot of the error page shown to Firefox users

Comment 3

[Randell Jesup [:jesup] (needinfo me)]

Seems like an older site; references Chrome 63, under windows doesn't mention Windows 11. That doesn't mean it isn't used, though

Comment 4

[Randell Jesup [:jesup] (needinfo me)]

UA spoof gets you to main page, but I think you need a chinese? +86 phone number to register.
We could try UA-spoofing it as a blind fix if we can't contact someone using the service

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

alidocs.dingtalk.com is in the 100000 cohort in CRUX (i.e. it's in the 10000 to 100000 grouping of sites globally). Very likely it's higher in China(?) and perhaps some other asian countries, since it's not translated and you need a +86 (China) phone number to register.

Comment 7

[Maire Reavy [:mreavy]]

Once we ship an intervention, this should become an Outreach bug.

Comment 8

[Thomas Wisniewski [:twisniewski]]

The URL provided is also showing the blocked message for me in Chrome, so I think we'll need another URL to work with.

Comment 9

[Daniel Holbert [:dholbert]]

Hmm, same for me now, using URL from comment 0.

This similar-but-not-quite-the-same URL from the duped webcompat issue still seems to redirect through to the login page in Chrome (vs. show the not-supported page in Firefox): https://alidocs.dingtalk.com/not-supported-env?goto=https%3A%2F%2Fdocs.dingtalk.com%2Fi

Comment 10

[Daniel Holbert [:dholbert]]

Here are the URLs I just tested:

1. https://alidocs.dingtalk.com/not-supported-env?goto=https%3A%2F%2Fdocs.dingtalk.com (from comment 0)
2. https://alidocs.dingtalk.com/not-supported-env?goto=https%3A%2F%2Fdocs.dingtalk.com%2Fi (from the see-also webcompat issue)
3. https://alidocs.dingtalk.com/not-supported-env?goto=https%3A%2F%2Fdocs.dingtalk.com%2F (same as 2 but with i removed)

The %2Fi on the end of #2 is just URL-encoded form of /i. It works in Chrome if I remove the i, too, as noted in #3. Perhaps they changed their redirector logic such that it expects a slash after the domain name, or something. Anyway, the good news is we've got URLs that repro the behavior-difference -- URLs #2 and #3 in this comment here, at least.