# Better copy for browser is "too old to work on this site"

**URL:** <https://meta.discourse.org/t/better-copy-for-browser-is-too-old-to-work-on-this-site/232968>\
**Category:** UX\
**Created:** [July 15, 2022, 12:47pm UTC](https://meta.discourse.org/t/better-copy-for-browser-is-too-old-to-work-on-this-site/232968 "2022-07-15T12:47:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ClawdiaWolf](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/clawdiawolf/32/262518_2.png) [@ClawdiaWolf](https://meta.discourse.org/u/ClawdiaWolf)\
**Post date:** [July 15, 2022, 2:09pm UTC](https://meta.discourse.org/t/better-copy-for-browser-is-too-old-to-work-on-this-site/232968/4 "2022-07-15T14:09:54Z")

</div>

Normally, Duecourse tries to detect unsupported versions via feature checking rather than UA sniffing.

A recent issue with the composer in older versions of Firefox required them to use UA sniffing because if you asked certain versions of Firefox they would happily (and technically accurately) say they supported the necessary functions when they are in fact buggy and don’t work properly.

The issue here is that Seamonkey is telling sites by default that it is compatible with a _much_ older version of Firefox rather than the version it is _actually_ compatible with.

Discourse is doing the right thing in this case.

---

_[View the full topic](https://meta.discourse.org/t/better-copy-for-browser-is-too-old-to-work-on-this-site/232968)._