# 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:** Product 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:** 1\
**Showing post:** 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!

---

_[View the full topic](https://meta.discourse.org/t/browser-detection-script-only-malfunctioning-on-pale-moon-32-x/273848)._