# Discourse not loading on legacy browsers

**URL:** https://meta.discourse.org/t/discourse-not-loading-on-legacy-browsers/221412
**Category:** Bug
**Created:** [March 19, 2022, 7:13am UTC](https://meta.discourse.org/t/discourse-not-loading-on-legacy-browsers/221412 "2022-03-19T07:13:00Z")
**Posts on this page:** 1
**Showing post:** 63

<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: [April 4, 2022, 10:01am UTC](https://meta.discourse.org/t/discourse-not-loading-on-legacy-browsers/221412/63 "2022-04-04T10:01:39Z")

</div>

> [@sam](#):
>
> remove, browser\_update\_user\_agents we don’t want to feature detect with that anymore

IIRC this was essential for some browsers (IE \< 10?) because it’s impossible to access `<noscript>` tags via JavaScript after doing the feature detection. I think @dan worked on this problem a few years back?

Note that there are two fallback ‘modes’ at the moment:

1. Serve the crawler view. No JS required. This is gated on `browser_update_user_agents`.

2. Serve the full app, feature detect, and fallback by moving `<noscript>` content into `<body>`. This is not based on user agent.

The problem here is that (2) is not working on mobile, because the server isn’t rendering any `<noscript>` content. We need to fix that, without breaking (1) for mega-old browsers.

---

_[View the full topic](https://meta.discourse.org/t/discourse-not-loading-on-legacy-browsers/221412)._
