Mozilla Firefox 125.0.2PL
Kod:
Zaloguj
lub
Zarejestruj się aby zobaczyć!
Apr 23, 2024
- New features:
- Implemented support for single-use <link rel=preload> meta tag. This implementation allows use of it without specifying a second <link rel={type}> meta tag to actually load the linked document which was originally intended for this tag (to hint to a browser it should pre-load the document for fast painting).
- Implemented CSP v3 keywords script-src-elem, script-src-attr, style-src-elem and style-src-attr.
- Enabled the use of html5's <dialog> by default. While this is not yet a complete implementation, use of it in the wild dictated we enable this early. The implementation should functionally suffice for usage seen so far.
- Added support for Emoji 15.1.
- Implemented webkitURL legacy window alias for URL for web compatibility.
- Implemented CSS shorthands margin-block, margin-inline, padding-block and padding-inline.
- Added support for querying CPU capabilities (SSE2/AVX/AVX2) to the Navigator interface. For privacy reasons this is not exposed to the web, but can be used by extensions.
- Changes/fixes:
- Fixed broken mousewheel scrolling if building with --disable-npapi.
- Fixed a minor issue with XUL tree display in some circumstances.
- Dev: Aligned canvas Path2D.addPath with the updated spec. It now supports DOMMatrix as opposed to SVGMatrix.
- Removed Stylo (Gecko Rust style system) leftovers from the source tree.
- Fixed a few potential emoji display issues.
- Fixed some issues with workers.
- Fixed an issue with ctrl+c copying in devtools.
- Fixed crashes when run under WINE because of its lack of support for IDXGIKeyedMutex.
- Fixed a crash when dealing with a specific (unmaintained) extension.
- Added .xrm-ms files to the executable warning list on Windows.
- Added sanity checks on http/2 header sizes.
- Fixed a potential issue in the JavaScript JIT compiler.
- Pulled a few fixes from upstream for the OpenType Sanitizer.
- Added a fix to avoid a potential issue when assigning a media data buffer.
- Security issues addressed: CVE-2024-3863, CVE-2024-3302, CVE-2024-3857 DiD, CVE-2024-3859 and CVE-2024-3861 DiD.
Changes
- The minimum CPU requirement has now been loosened. Any x86-64 processors with support for
Zaloguj lub Zarejestruj się aby zobaczyć!should now be able to run WaterfoxZaloguj lub Zarejestruj się aby zobaczyć!.- Various UI bug fixes.
- Updates to the tabs sidebar.
- Keep sidebar showing after leaving fullscreen mode.
- Respect user’s choice for browser.tabs.insertAfterCurrent and browser.tabs.insertRelatedAfterCurrent.
- Security fixes
Zaloguj lub Zarejestruj się aby zobaczyć!.Upcoming Changes
Zaloguj lub Zarejestruj się aby zobaczyć!to get access to Waterfox Privacy Search. We are currently testing in a closed Alpha, which will then be opened to general access in a Beta. Note: As it currently stands, this is a separate and optional product that will not be included in Waterfox.Footnotes
- After extensive testing, no noticeable performance difference was observed on CPUs with SSE3 support compared to those with SSE4.1. This change aims to improve compatibility and accessibility for a wider range of users.
Zaloguj lub Zarejestruj się aby zobaczyć!
v33.1.1 (2024-05-28)This is a minor security and stability update.
Changes/fixes:
- Made the nonce length for http digest auth configurable.
- Fixed various potential issues with font loading, parsingand handling.
- Cleaned up error reporting for workers and normalized errormessages.
- Security issues addressed: CVE-2024-4772 DiD, CVE-2024-4771,CVE-2024-4769 and CVE-2024-4770.
- We've switched back to an older toolchain (17.3) forcompiling 32-bit Windows binaries (again) to hopefully address some ofthe intermittent stability issues people continued to have on laterMicrosoft compiler versions when running on older hardware.
Jun 18, 2024
- New features:
- Implemented the missing parts of the html5 <dialog> element, including modal handling and custom backdrops.
- Implemented courser, user-configurable granularity for the canvas poisoning anti-fingerprinting measure. See implementation notes.
- Implemented new CSS viewport units svw, svh, svmin, svmax, lvw, lvh, lvmin, lvmax, dvw, dvh, dvmin and dvmax.
- Implemented new CSS logical viewport units vb, vi, svb, svi, lvb, lvi, dvb and dvi.
- Changes/fixes:
- Removed the archaic and wholly outdated FIPS security module code.
- Removed the archaic DBM support code for storing of passwords in DBM format files.
- Removed the -moz prefix from -moz-fit-content, aligning with the current CSS standard fit-content value.
- Updated our build system by adopting parts of the old autoconf 2.13 as maintained code. autoconf 2.13 is no longer a build requirement. If you build from source, you may want to review your dependencies with this change.
- Fixed issues when building with GCC 14.* and Clang 16.*.
- Fixed issues with emoji sequence clusters causing incorrect rendering of emoji glyphs in some cases.
- Made some arguments to the legacy XPathEvaluator/XPathExpression interfaces optional for web compatibility.
- Fixed a crash when reporting JavaScript module exporting errors.
- Updated checking of special cookie prefixes to be case-insensitive in accordance with the current RFC 6265 (bis-11+).
- Fixed issues with external protocol handlers.
- Fixed an issue where autocomplete pop-ups would stay open in some circumstances.
- Fixed an issue with potentially bad file names being entered by the user to "Save As...".
- Fixed several crashes and race conditions.
- Security issues addressed: CVE-2024-5699, CVE-2024-5702 DiD, CVE-2024-5690, CVE-2024-5698 DiD, CVE-2024-5688 DiD, CVE-2024-5692 and several other security issues (some more DiD) that do not have CVE numbers assigned to them.
- Implementation notes:
- While we have had canvas data poisoning as an option for a very long time (we introduced it as a concept), it was pointed out that having a fast rotation on the poisoning leading to new and unique canvas hashes every time a user would navigate was a red flag to trackers that poisoning is being employed, mitigating its intent. A different implementation of canvas poisoning was created that will still provide human-imperceptible data manipulation of canvases leading to bogus hashes for trackers, but now in such a way that this hash will not change for a courser, but variable time frame. This time frame defaults to 5 minutes in this release, which may be tweaked in the future if necessary, but is also entirely user-configurable between 1 second and 8 hours with the preference canvas.poisondata.interval (indicated in seconds).