I believe that Vector 2022 ought to work fully on at least the above browsers, because they include the last versions available for millions of highly-capable pre-2009 Mac computers stuck on lower MacOS versions, such as my 64-bit multi-GHz multi-core Intel 2008 MacBook OS X 10.6.8.

Per https://www.mediawiki.org/wiki/Compatibility#Browser_support_matrix I'm not sure that's within the policy...

As a workaround, people who are still on such insecure outdated systems using insecure outdated browsers could switch to using another MediaWiki skin instead.

Jdlrobson closed this task as a duplicate of T313066: Improve grade C version of Vector 2022.Mon, Jan 23, 2:36 PM

Thank you; agreed.

As a workaround, people who are still on such insecure outdated systems using insecure outdated browsers

They're not insecure if one secures them. Many of our systems are perfectly secure.

could switch to using another MediaWiki skin instead.

Ineed, I use Applescript to append ?useskin=vector to URLs when I need the Contents nav.

Aklapper renamed this task from Vector 2022 display issues on some MacOS browsers to Vector 2022 display issues on some ancient browser versions on old MacOS versions.

Calling secure systems "insecure" and 2017 software "ancient" is neither helpful nor factual, just name-calling.

Calling secure systems "insecure" and 2017 software "ancient" is neither helpful nor factual, just name-calling.

Firefox 45.9.0esr saw it's end of life 67 months ago. It's extremely likely (and thus "factual") that some of the hundreds of security issues fixed since June 2017 only in later Firefox releases also apply to that 45.9.0esr codebase.