Updated LibVPX to 1.4.x to be able to play more kinds of VP9-encoded videos.
Updated the JPEG decoder library to 1.4.0.
Fixed and cleaned up XPCOM timer thread code to avoid intermittent issues with events not firing (especially after stand-by).
Updated overrides to work around issues with Facebook and Netflix.
Fixed an issue where too-old system-supplied NSPR and/or NSS libraries would be accepted for use.
Updated the libpng library to 1.5.24 to address critical security issues CVE-2015-7981 and CVE-2015-8126
Updated the NSPR library to 4.10.10 to address several security issues.
Updated the NSS library to 3.19.4 to address several security issues.
Fixed a memory safety hazard in SVG path code (CVE-2015-7199).
Fixed an issue with IP address parsing potentially allowing an attacker to bypass the Same Origin Policy (CVE-2015-7188).
Fixed an Add-on SDK (Jetpack) issue that would allow scripts to be executed despite being forbidden (CVE-2015-7187).
Fixed a crash due to a buffer underflow in libjar (CVE-2015-7194).
Fixed an issue for Android full screen that would potentially allow address spoofing (CVE-2015-7185).
Added size checks in canvas manipulations to avoid potential image encoding vulnerabilities like CVE-2015-7189. DiD
Fixed potential information disclosure vulnerabilities through the NTLM authentication mechanism. Insecure NTLM v1 is now disabled by default, and the workstation name is set to WORKSTATION by default (configurable with a preference for environments where identification of workstations is done by actual reported machine name). This avoids issues like CVE-2015-4515.
Fixed a potentially vulnerable crash from a spinning event loop during resize painting. DiD
The news bulletins for that flaw came out yesterday.
The only addons that don't work are those that do explicit version checks without actually depending on the version, and those that rely on australis (they work but have no icon).
The real question is, which addon do you use that doesn't work with palemoon?
Trick question: the answer is none.
>yfw there are tons of critical holes in nevest firefox that will be fixed next release but now everyone is vulnerable no less then ff28
enjoy your placebo
It's pretty dead already. The update that breaks all existing add-ons will probably be a final nail in its coffin.
Shame. Would Pale Moon be able to carry on FF's legacy all alone?
>Would Pale Moon be able to carry on FF's legacy all alone?<neonfuz> MoonchildPM: is it hard to bring features from firefox to palemoon nowadays?
<@MoonchildPM> neonfuz: It's a challenge. Mozilla does a lot of refactoring for the sake of refactoring.
<neonfuz> MoonchildPM: if pulling code from firefox becomes nearly impossible for palemoon, will palemoon die?
<@MoonchildPM> No, of course not.
They've got the determination, at least.
>pocket proprietary botnet
>no status bar
>no download speed in download status
>2px-wide url bar
>no new tab page options
>dem memory leaks
>dat slowass everything
>security flaws out the box (pdfjs, unresolved CVEs)
>getting this butthurt about people not accepting cancer into their lives
If you're not defending firefox THIS hard due to the pony, then what? It's pretty obvious you're a ponyfucker.
You seem discontent. Perhaps you should go back to watching your children's cartoon to calm you down before you come back. I know that the fact there are ponies in firefox excites you, but please contain your autism.
>It's been 5 years
>people still get triggered by ponies