# Browser detection script (only!) malfunctioning on Pale Moon 32.x

**URL:** https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848
**Category:** Support
**Created:** [August 3, 2023, 3:51pm UTC](https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848 "2023-08-03T15:51:57Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![TuggyNE](https://avatars.discourse-cdn.com/v4/letter/t/839c29/32.png) [@TuggyNE](https://meta.discourse.org/u/TuggyNE)
#### Post date: [August 3, 2023, 3:51pm UTC](https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848/1 "2023-08-03T15:51:57Z")

</div>

On the majority of Discourse instances I visit with Pale Moon 32.x, I initially get a crippled view with a “browser too old” banner at the top. However, this is a false positive from the browser-detect JS, since using an adblocker to disable `/assets/browser-detect-<hash>.br.js` allows full functionality from the sites. (As expected, since Pale Moon supports most modern web standards.)

In other words, you’ve successfully written a site that will work on modern browsers, but then arbitrarily limited it to a handpicked selection of them with user agent sniffing from the 90s. This has the unintended side effect of limiting user freedom and propping up Google’s near-monopoly on the web. Please fix this!

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 3, 2023, 3:55pm UTC](https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848/2 "2023-08-03T15:55:25Z")

</div>

We don’t arbitrarily limit browsers. We use feature detection to determine whether a browser supports all the modern web APIs which Discourse relies on. Our current checks are:

> <https://github.com/discourse/discourse/blob/78369c94c1c9606e77bf43718a23425bce9fb3a3/app/assets/javascripts/discourse/scripts/browser-detect.js#L4-L12>

So, Pale Moon must be missing one of those features.

---

<div class="post-metadata">

### Author: ![TuggyNE](https://avatars.discourse-cdn.com/v4/letter/t/839c29/32.png) [@TuggyNE](https://meta.discourse.org/u/TuggyNE)
#### Post date: [August 3, 2023, 4:04pm UTC](https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848/3 "2023-08-03T16:04:51Z")

</div>

Ah, I see. Thanks for the prompt reply, and correcting my misconceptions!

Only `CSS.supports("aspect-ratio: 1")` is false. I have to admit it puzzles me that you would need to detect that, especially since as I went looking to see what styles rely on that, I found quite a few places in the CSS with `@supports not (aspect-ratio: 1) {/*...*/}` blocks and the like, which would seem to explain why the sites’ appearance is fine despite lacking `aspect-ratio` support. (I’ve never noticed any visual problems anywhere despite using Discourse extensively in both PM and in other browsers.)
