> but why would you actively block them? From first-hand experience, I've seen it happen in SaaS orgs with (diplomatically speaking) "unsophisticated-but-confi

> but why would you actively block them? From first-hand experience, I've seen it happen in SaaS orgs with (diplomatically speaking) "unsophisticated-but-confident" userbases seeking to reduce support-costs. The kind of SaaS where the paying customer is a business - and where the users' eyes glaze-over any warning banner or message but eagerly call the SaaS support number for entirely unrelated issues with Outlook; so outright blocking unsupported browsers/clients reduces the support burden. (I'm not defending this practice; I'm strongly opposed to it) ---- Another (also, unfortunately, from first-hand experience) reason is a (very) non-technical project leader will write up a (semi-reasonable) brief Jira ticket like "Our SaaS product doesn't work in Firefox; until we invest in supporting Firefox we'll just direct users to use a supported browser" - but the ticket gets assigned to a particular kind of remote contractor SWE who never challenges higher-ups or says "this is a bad idea" - who'll interpret the part about "we'll direct users to use a supported browser" as "block unsupported browsers".