Maybe it’s just me, but I’ve tested on several mobile devices. These devices are using a legacy version of Firefox 68.11.0, the last one before Mozilla botched the UI. As of some point on Monday or Tuesday this week, I can no longer see the content of community.jenkins.io…
The pages (main page, /latest, or a known topic) appear to take some seconds to load but then are blank. Switch to Request Desktop site or View source also gives a blank page. This most likely affects not just FF on Android, but a number of other legacy browsers, assuming this is a similar issue that broke StackExchange last month (for the second time).
I recognize we can’t have legacy support forever, but S/E fixed it once before and we hope they do again. As for here, wondering if anyone admins know what could have changed this week and if anything can be done. Alternatively, with that info, do I report it to Discourse? Some version info would help to report.
we don’t manage any of it, its sponsored by the official discourse group, so they’ll know what version we are using and everything. We are in the EU 2 datacenter. Meta tag in the header/source says Discourse 2.9.0.beta2
We don’t get told about any upgrades applied. And I created a new category and group this week, but I don’t think either could contribute to slowness.
Interestingly, I fired up a WINXP PC running FF 52.9.0 ESR and notwithstanding the banner “your browser is too old to work in this site”, the site appeared to load fine, so it seems rather specific/esoteric.
@halkeye , today Discourse appears to have applied a fix, but it’s only partial.
The site now displays a “browser is too old” banner, the logo, the footer and in the case of this site, the Categories (w/totals). But no actual topics are displayed. Discourse has not categories, so just no topics displayed.
No idea how to provide any more details to them. Could you possibly retry whatever you did w/saucelabs and see what it produces now?