Google published the release of Web-browser Chrome 132. At the same time a stable release of a free project Chromium acting as the basis of Chrome has been made available. Chrome browser differs from Chromium in various aspects such as the use of legotpes OGLE, a notification system in case of collapse, DRM modules for protected video content, automatic installation system of updates, Sandbox insulation, Google API key provision, and transmission of RLZ parameters during searches. The Extended Stable branch is available for users who need more time to update, accompanied by 8 weeks. The next Chrome issue, Chrome 133, is scheduled for February 4.
The main changes in Chrome 132:
- Added heuristics that automatically include the “HTTPS-FIRST” function, redirecting HTTP sites to HTTPS for users who frequently use https. Users can disable this mode in settings if they do not wish to activate “HTTPS-FIRST”. When using “HTTPS-FIRST”, if a site does not support HTTPS, requests are made through HTTP with the option to revert to HTTPS if necessary or in case of certificate issues. A warning is displayed if HTTPS is not accessible before opening a site through HTTP.
/Reports, release notes, official announcements.