Users reported that forums running on Discourse, including forums.sketchup.com and meta.discourse.org, stopped rendering on iPads running iOS 9.3.5, displaying only a white screen with JavaScript errors CoIin. The issue appears to have emerged within the last month, coinciding with recent updates to Discourse’s codebase, which no longer officially supports iOS 9 due to its age and lack of modern browser features sam. While users cannot easily patch Discourse to restore compatibility themselves, Discourse team member j.jaffeux identified and committed a fix, which was first tested successfully on meta.discourse.orgCoIin. The fix will be deployed to forums.sketchup.com within hours sam. Discourse aims to maintain a clean codebase by avoiding polyfills for outdated browsers, but may explore fallbacks to a “readonly” view for unsupported devices in the future sam.
The person reporting the problem has an iPad just for viewing the forum I think, and it happens to be old enough that 9.3.5 is the latest he can be on.
Was there a recent change that would explain why it no longer works?
Thanks. How about the timing, is it just in the last few days that you did something that would break iOS 9? The iPad owner says the forum was ok last week.
Also, are all forums based on your software obliged to follow your minimum requirements, or can they do their own patches to stay compatible?
It is likely to be something that happened in the last month and a bit, we don’t deploy our hosted enterprise customers as aggressively as we deploy this site (which is deployed every commit).
There have been some changes that could have caused this, @j.jaffeux will report back in the next day or so.
As to forking or patching to get compatibility, this is not an easy task. Discourse is a pretty rich application and we tend to take advantages on modern browser facilities, this is a moving target. We do not like complicating our internal code to work around browser spec deficiencies, we only do so when we have no choice.
That said, we are pretty committed to have a readonly view for crawlers, so for example:
If you somehow want to fallback to “readonly” view for browsers that are not supported (instead of sorry, browser is not supported) this is work I would not mind exploring, shoot us off a separate message here to @team