JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents

1. platform.js

   1 2 3,200 0.0 JavaScript

   Discontinued A platform detection library.

   

2. AppSignal

   www.appsignal.com sponsored

   AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.

   

3. eslint-plugin-compat

   2 8 3,183 7.1 TypeScript

   Check the browser compatibility of your code

   

   eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature.

   [0] https://github.com/amilajack/eslint-plugin-compat

4. stylelint-no-unsupported-browser-features

   3 3 453 5.4 JavaScript

   Disallow features that aren't supported by your target browser audience.

   

5. stylelint-no-unsupported-browser-fe

   4 1 - -

6. ua-client-hints

   5 14 623 4.4 Bikeshed

   Wouldn't it be nice if `User-Agent` was a (set of) client hints?

   

   As a Firefox/FreeBSD user occasionally annoyed by this nonsense, but not being knowledgeable about modern web standards evolution, I wonder if https://wicg.github.io/ua-client-hints/ will fix this by killing User-Agent headers.

7. chromium-legacy

   6 38 424 0.0 C++

   Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

   

   It's not just banks. Google Maps will refuse to work if you're running OS X Lion, even if you're using a fully up-to-date version of Chromium[1] which is just as capable as any other Chromium-based browser on any other operating system.

   Google Maps work perfectly on Lion if you fake the user agent, because of course it does, it's a web app and the underlying OS is irrelevant.

   1: https://github.com/blueboxd/chromium-legacy

Suggest a related project