“Chrome 109 is the last version of Chrome that will support Windows 7 and Windows 8/8.1. Google will stop supporting Windows 7 and Windows 8.1 on February 7 when the company ships Chrome 110. Either way, the browser will stop working on the two platforms next year, so it’s all just a matter of time until Windows 7 and 8.1 users have to look elsewhere for a browser that still works on their platforms. Some plug-ins have 64-bit support already.The number of browsers running on Windows 7 is shrinking at a very fast pace, and after Google announced the EOL for Chrome on this operating system, the next in the queue should be Mozilla and Firefox browser.Īs the main alternative to the invasion of Chromium-powered browsers, Mozilla Firefox continues to be one the most popular browsers out there.īut as GHacks noticed recently, Mozilla is yet to decide when it plans to drop the support for Windows 7 and 8.1, as the company has been looking into the matter for several years already.Īfter Google’s announcement in October, Mozilla’s talks on this front gained more pace, with a decision in this regard expected sooner rather than later.Īt this point, it looks like the end of support for Mozilla Firefox on Windows 7 and Windows 8.1 could take place either in January 2023 or in June 2023.We do not intend to drop support for 32-bit Firefox.We do not need or expect memory use parity with 32-bit Firefox.We do not immediately need a stub installer or website magic to deliver 64-bit builds to 64-bit Windows users. ![]() We should not attempt support of 64-bit Windows XP (neither x86-64 nor Itanium).Stability parity with 32-bit Firefox on Windows.Performance parity with 32-bit Firefox on Windows.AUS changes to support 64 and 32-bit builds and updates.QA automation able to test 64 and 32-bit builds.Build automation able to create 64 bit builds.Coherent 32 bit plugin on 64-bit build experience.QA will have one more platform to test.Rel Eng will need to update systems for build, automation, and updating.Platform engineering resources are needed to implement running 32-bit plug-ins in 64-bit Firefox.But the 32-bit builds can only use part of the user's memory address space and so we are not taking full advantage of the user's platform capabilities. Users with 64-bit Windows 7 (and Vista) can currently use Firefox 32-bit builds and that's what we offer them. This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.) There are potential performance benefits as well - especially in JavaScript land. It would help dramatically with OOM crashes due to address space exhaustion. Offering a x86 64-bit Firefox to Windows 7 (and Vista) 64-bit users brings one immediate and major improvement. Not sure what to do if users have both 32-bit and 64-bit Firefox installed.That would break if they inject a 32-bit DLL into a 64-bit process. Some of the ATs inject their own DLL into Firefox's address space. Accessibility support will be an issue here.We do not want users to have a worse view of 64-bit builds than they do of 32-bit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |