Email or username:

Password:

Forgot your password?
Top-level
kitsune

@downey instead of flat out locking people out, it should be standard to instead have "It appears you're using an unsupported browser, use firefox chrome blah blah blah, click here to proceed anyway, some elements may not appear or work correctly"

14 comments
Michael Downey 🚩

@kitsune

💯

I don't mind a disclaimer or reminder.

But this is an anti-pattern I've seen start to creep up on several web sites lately.

DELETED

@downey @kitsune 1996: "You can't see this website, you don't have a kewl browser, upgrade to Netscape v1.π today"

2023: "You can't see this website, you have a stale icky browser, upgrade to advanced adware today"

rus

@dpnash @downey @kitsune there was also a period of time when you had a *more* advanced browser, say Netscape 3, and you'd get the same error as some of those pages looked for specific matches.

iAmAnEngarneer

@downey @kitsune godaddy login blocks me on linux in chrome and firefox, so thats bad.

Michael Downey 🚩

@engarneering to think that they used to show up to open source conferences....

@kitsune

Brett Sheffield (he/him)

@kitsune @downey A competent web dev would test for browser features. There is never a good reason to look at the User-Agent string.

Hanneke

@dentangle @kitsune @downey A competent dev *with enough budget*. But they should never lock one out though.

Dasy2k1

@dentangle @kitsune @downey

Although warning if they are using ie7 or earlier that you can't guarantee that your layout isn't completely janky on browsers that are not standards compliant is fine

Irina

@dentangle @kitsune @downey I learned to hack the User-Agent string in the late 1990s when I got locked out of websites for not using IE. (Which I couldn't. Because Linux.)

Norman Wilson

@kitsune @downey If their elements won't work in my browser because they didn't stay within the HTML standard, the problem is not my browser but their competence.

Go Up