Pale moon as a fork of Firefox isn’t supported by the main Discourse team. I can look at patching it as it looks for the Goanna rendering engine already, but they’d probably reject my update (as to not get into the support of that browser, rightly or wrongly) and then we’d need to fork our own Discourse source. Which then means we need to merge our own security/features in every update (weekly or so), which is no fun and untenable if I get hit by a bus.
So basically not ideal, as it’s not a supported browser. Sorry wheels.
Thank you for the info @Fridge.
I would never expect you to branch off into custom versions of the software @fearlessfrog. Keeping current versions running has to be a big enough headache.
However I am having the same problem using the same Win 7 machine using the Internet Explorer 11 browser. (Image was added just to confirm I was using Internet Explorer)
When I logout from this session I will check to see if I have this same logout problem using my WIn 10 machine that has the Edge and Firefox browsers next and get back to you. I could see them dropping support for IE too but not the Edge and FIrefox browsers. If that machine doesn’t work a bug report might be in order.
Yep, the menu is new, so could be buggy. If you find that do report it.
EDIT: Looks like it is getting fixed for IE11, so that’s good. We’ll update when done. Microsoft’s support for Win7 stops Jan 2020, and the Discourse team plan to stop support for IE11 on June 2020 as well.
Just for fun, I did a lookup in the logs of browser user agents over the last little while for here.
There is one other person who uses the Palemoon browser @wheelsup_cavu, so you might have a twin out there (with goatee?).
Just thought I would throw in that the menu is working from my iPhone on iOS 13.2.3 (latest) with Safari.
For anyone that doesn’t know:
Cool to see how the forum handles that!
I am working with Magento 2 at work, which has its own similar mechanism - but even then when doing updates I have noticed the browser doesn’t get the new content and a hard refresh solves it.
All static content is kept in a local cache with a version number. Ie, URL/pub/media/static/version1571429888/sub folders/