app.101edu.co - Firefox is unsupported browser

[webcompat-bot]

URL: https://app.101edu.co/lti?lti=true

Browser / Version: Safari 13.1 Operating System: Mac OS X 10.15.4 Tested Another Browser: Yes Safari

Problem type: Site is not usable Description: Browser unsupported Steps to Reproduce: Not really. I need it for my class homework, but it doesn’t want to work due to the browser not being supportive.

Browser Configuration

• None

From webcompat.com with ❤️

[softvision-oana-arbuzov]

Thanks for the report, I was able to reproduce the issue.

Note:

1. The issue is not reproducible on Chrome.
2. The issue is also reproducible on Safari.

Tested with: Browser / Version: Firefox Daylight 36.0 (5732) Operating System: iPad Mini 4 iOS 14.6 (1536 x 2048 pixels (~324 ppi density))

Moving to Needsdiagnosis for further investigation.

[karlcow]

The same thing seems to happen on Safari? This is what I get on Safari Desktop.

So at least this is logical that Firefox on iPad get the same treatment as they share the same rendering engine. Now the issue is more why they thought/needed to block the WebKit rendering engine.

[karlcow]

The trigger is here.

export default function SupportedBrowserWall(props) {
    if (isSupported()) {
        return props.children;
    } else {
        return renderUnsupportedView();
    }
}

with

function isSupported() {
    if (OS != 'web') {
        return true;
    }

    let agent = window.navigator.userAgent;
    if (agent.indexOf("Version") != -1 && agent.indexOf("Safari") != -1) {
        return false;
    }
    return true;
}

So this is simple user agent detection blocking Safari without explanations. Quite unfortunate.

If I fake Firefox UA on Safari, I get the login screen.

[karlcow]

At least they need to be contacted to understand why they block Safari.

[webcompat-bot]

Generate outreach template

[karlcow]

Their email address is hello@101edu.co

[karlcow]

Reported on WebKit too https://bugs.webkit.org/show_bug.cgi?id=229980

[mozilla829]

Email sent to address provided by karlcow

[mozilla829]

Response from website:

As you can see from the error message, our site is optimized for both Firefox and Chrome. We will pass the bug report along to our engineering team to see what could be causing this issue.

I wanted to quickly address the github question about Safari -- the reason it's blocked is because some of the types of React Native coding used on the site doesn't play well with Safari. So, in order to make sure everything actually runs on the browser you're using, Safari is blocked. I imagine if you did bypass this block, you might be able to access a portion of the site, but the interactive questions with drag and drop and selection areas would either not load or not work correctly, so we definitely do not suggest using Safari.

[karlcow]

@Justin-Weinberg @Allicolyer

About

I wanted to quickly address the github question about Safari -- the reason it's blocked is because some of the types of React Native coding used on the site doesn't play well with Safari. So, in order to make sure everything actually runs on the browser you're using, Safari is blocked. I imagine if you did bypass this block, you might be able to access a portion of the site, but the interactive questions with drag and drop and selection areas would either not load or not work correctly, so we definitely do not suggest using Safari.

Could you or someone on the Engineering team share with Apple what the is the specific bug you ran into with Safari? You may follow up here or on https://bugs.webkit.org/show_bug.cgi?id=229980 as you may see fit. That would help a lot improve WebKit/Safari if possible.