Pale Moon 32 has been released!

[Moonchild]

This is a new milestone release.
Primary focus for this milestone is web compatibility, in particular Regular Expression extensions, standards compliance issues and further JPEG-XL support.
This milestone now offers full coverage of the ECMAScript 2016-2020 JavaScript specifications, with the exception of BigInt primitives.
Special thanks to Martok, Job Bautista and FranklinDM without whom this milestone would not have been possible, and to dbsoft for putting in the effort to work on Mac and FreeBSD builds.

Most important changes:

• Implemented Regular Expression named capture groups.
• Implemented Regular Expression unicode property escapes.
• Re-implemented Regular Expression lookaround/lookbehind (without crashing this time ).
• Implemented progressive decoding for JPEG-XL.
• Implemented animation for JPEG-XL.
• Renamed CSS offset-* properties to inset-* to align with the latest spec and the web.
• Fixed CSS inheritance and padding issues in some cases.
• Aligned parsing of incorrectly duplicated HSTS headers with expected behavior (discard all but the first one).
• Implemented a method to avoid memory exhaustion in case of (very) large resolution animated images.
• Updated the JPEG-XL and Highway libraries to a recent, stable version.
• Cleaned up some unused CSS prefixing code.
• Improved the ability to link on *nix operating systems with other linkers than gcc's default.
• Stability improvements (potential crash fixes).
• Security issues addressed: CVE-2023-23598, CVE-2023-23599 and several others that do not have a CVE number.
• UXP Mozilla security patch summary: 4 fixed, 2 DiD, 19 not applicable.

Platform support:

We're working on finalizing official builds for Mac OS and FreeBSD. These are currently in beta and can be downloaded from the Contributed Builds page. Please note that you may run into some system compatibility issues with these builds. If you do, please report it in the appropriate board!

Linux builds will follow shortly!

[Moonchild]

One important implementation that was missed in the original release notes was the fact that we now also have a workaround for the infamous <button> issue where websites are non-compliant due to Google Chrome treating <button> elements like generic containers, contrary to the HTML standard.

The release notes have been updated accordingly now, and here is the implementation note to go along with it:

To provide users with a temporary work-around for non-compliant websites, a compatibility mode for <button> elements was implemented, which will treat <button> elements as generic containers instead of actual form button elements. This has been necessary because Chrome is not standards compliant in this respect and website developers regularly make the mistake of trying to use active content on button faces and expecting pointer events to end up being sent to the active content and not the button (which is not what the standard prescribes! See "content model" on the standards page stating there "must be no interactive content descendant"). Webmasters should be alerted to this compliance issue, but it can (temporarily) be worked around in the browser from this point for forward by setting the preference dom.forms.button.standards_compliant to false and restarting the browser. Note that this is a workaround and the only actual solution is advocacy for the standard and more browsers becoming standards compliant.