# Mobile (iOS) pages blank with JS disabled

**URL:** <https://meta.discourse.org/t/mobile-ios-pages-blank-with-js-disabled/266240>\
**Category:** Bug\
**Tags:** pr-welcome\
**Created:** [May 25, 2023, 5:27pm UTC](https://meta.discourse.org/t/mobile-ios-pages-blank-with-js-disabled/266240 "2023-05-25T17:27:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [May 26, 2023, 5:40pm UTC](https://meta.discourse.org/t/mobile-ios-pages-blank-with-js-disabled/266240/3 "2023-05-26T17:40:19Z")

</div>

> [@sam](#):
>
> @Falco / @david I believe this is the optimisation we have for mobile where we don’t send the full payload to save on traffic?

Yes, that’s exactly it. The trade-off is better performance for 99.999% of users, with saves for both network usage and user battery, but people who disable JS on their modern smarthphones don’t get the static HTML version.

> <https://github.com/discourse/discourse/blob/main/app/helpers/application_helper.rb#L434-L436>

> [@sam](#):
>
> Feels deliberate, but maybe there is something we can do here longer term and force a redirect or something for cases like these? (redirect to ?javascript\_disabled or something…)

Force a redirect with a `meta` tag? Maybe we render a button on the `else` of this `if` here

> <https://github.com/discourse/discourse/blob/main/app/views/topics/show.html.erb#L36>

that reloads the current page with a parameter and/or setting a cookie?

Considering the impact here, and the work needed, I’d say it’s low priority work and #pr-welcome.

---

_[View the full topic](https://meta.discourse.org/t/mobile-ios-pages-blank-with-js-disabled/266240)._