Keeping the Firefox bug report alive with more activity may help get this on their radar. It may also be a Discourse issue (or combination)
I tried this a couple of times as well but in some cases the specific tab is just āfrozenā and loading another page also does not work.
Iām on v121 by the way.
My only other browser is Chrome, and there I can access the forum without issues.
Since my last post I encountered a situation where nothing, even Quit, allowed me to load Discourse pages. I resorted to installing Vivaldi which works.
However I now find that pages are loading properly again in FF (121).
Fingers crossed for the next update!
I donāt think itās on their radar (anymore). It may be best to leave feedback in the Mozilla bug report.
Iāve pinged the Mozilla bug triage owner, letās see it if leads to some activityā¦
This issue happens less frequently for me, I actually donāt know when it happened for the last time. Anyone else?
I agree, havenāt seen it for some time. Letās pray it stays like this!
It has been months without issues for me as well.
I had switched to Chrome because of that issue, at least with the community forum. I will try with Firefox again, now. Thanks for your comments
Much better here too, though I do still see the occasional blockage. Monthly? I use computers more than the phone though.
Iāll report the next time it happens.
Same for me.
I donāt have blank page since months, I think.
For me it happened again, this time only a few reloads would be enough to fix this, but I reverted back to Chrome for the forum.
As promised, just reporting on another failure to load FP forum pages in Firefox. I checked I was able to load them in other browsers. I used my old āDelete browsing data on quitā option successfully (reloads unsuccessful). No special context info to convey.
For me, it was almost always sufficient to just ādiscardā Firefox from the app list. Sometimes I had to do it several times, but it usually worked in the end. It also helped to switch to a non-problematic tab before closing FF.
I think this issue is fixed