@xper Where are the most recent comments posted here in this (https://msfn.org/board/topic/187835-my-browser-builds-part-6/page/7/#comment-1289221) thread since Monday? And for your information, since your software update, MSFN has been completely broken in all of @roytam1 ’s browsers. There doesn’t seem to be a fallback mode when it comes to a bit older browsers, especially non-Chrome browsers like Pale Moon/New Moon which have been working fine on MSFN for years.

59 minutes ago, AstroSkipper said:

@xper Where are the most recent comments posted here in this thread since Monday?

https://msfn.org/board/topic/187862-server-forum-upgrade/

There doesn’t seem to be a fallback mode when it comes to a bit older browsers, especially non-Chrome browsers like Pale Moon/New Moon which have been working fine on MSFN for years.

What do you expect me to do? Because of old software, I had terrible problems with the server. Surely you don't expect me to develop compatibility for Pale Moon or any other browser? The development of the forum software is not in my hands. End of story. Period.

17 minutes ago, xper said:

What do you expect me to do? Because of old software, I had terrible problems with the server.

Pale Moon and New Moon 28 are not old software. And they have nothing to do with your server problems. It’s more likely the thousands of bot accounts that you still haven’t deleted and which are growing in number every few hours. But I’m not keen on repeating myself all the time.

23 minutes ago, xper said:

Surely you don't expect me to develop compatibility for Pale Moon or any other browser? The development of the forum software is not in my hands.

You do not have to develop anything. Rather look here https://github.com/Feodor2/Mypal68/issues/733#issuecomment-5380000877:

While there's a missing feature in mypal you can try contacting the MSFN staff to fix it on their side:

Proper fix (site-side, worth reporting to MSFN staff)
IPS's theme needs, inside the existing fallback @supports, a polyfill-safe duplicate of the
dead rule — escaped class instead of the pseudo-class, plus set --_anchor-v-fixed on open
(they already set it on close) so position:fixed is also scroll-correct:

@supports not selector(:popover-open) {
  i-navigation-menu:defined .ipsNavBar > li > .ipsNav__dropdown {
    position: fixed; left: 0;
    top: var(--_anchor-v-fixed, var(--_anchor-v));
  }
}

…mirroring the rule they already ship for generic i-dropdown elements.

Edited Sunday at 11:39 AM2 days by AstroSkipper

Invision Community Dropped Legacy Engine Support

Modern versions of Invision Community (especially Invision 4.x and the newest Invision 5 infrastructure) are heavily built on modern JavaScript frameworks, CSS grid variants, and Progressive Web App (PWA) components.

• Pale Moon uses the Goanna engine (a legacy fork of Mozilla's older Gecko engine).

• Because Pale Moon does not natively compute or follow modern JavaScript ECMAScript standards at the same pace as Chromium or standard Firefox, interactive features on your forum will completely shatter.

• Features like the text editor box, notification drops, AJAX content loading, and login popups will continuously throw errors or appear blank to Pale Moon
  
  Running an Invision Community forum while catering to users on legacy or non-standard browsers like Pale Moon creates an impossible web development conflict.

  You should treat Pale Moon issues as an unfixable, client-side problem rather than something you need to resolve on your server.
  
  Turning features off on server to cater to one or two Pale Moon users strips security and optimization benefits away from the 99% of your community navigating via Chrome, Safari, or Firefox.
  
  I don't have time for arguing. End of discussion. You don't like it? You have other forums.

This is going to be one of those unfortunate things where despite MSFN focusing not only on modern versions of Windows, but also legacy versions of Windows, we cannot always keep the forums accessible to legacy Windows and browsers. Your mileage may vary, but as the web evolves and security holes are found, we need to keep up with those new standards and fixes.

This is going to be more of what Invision supports, rather than xper. He can only do so much to keep the forums functional, but also safe. The web is a much different place than when I joined the forum 16 years ago and with attackers becoming more sophisticated, along with the use of AI, it's imperative to keep everything up to date. While Pale Moon is still being developed, it's still legacy enough where the developers will need to make changes to the underlying engine or more sites are just going to start breaking as the years go on. As much as many don't like it, progress doesn't stop, it's just a fact of life unfortunately.