estatehwa.blogg.se - Google chrome update history

NOTE: M82 release was cancelled due to cancellation of Chrome 82 release.What’s new in Google Chrome 114: Transparent navigation bar for Android Google wants to make the switch to its password manager painless Google wants to make the switch to its password manager painless Chrome 114 finally has a transparent navigation bar on Android Chrome 114 finally has a transparent navigation bar on Android Chrome's upcoming Reading Mode looks nothing like the others Google Chrome on PCs could add icons to the overflow menu Chrome has a solution for sites constantly asking to prove you're human Google really wants you to store your passwords in Chrome Google is trying to get rid of Chrome’s HTTPS lock icon again Google Chrome tests Material You theming on desktop Google Chrome is testing a new single-row layout for shortcuts on desktop This new Google Chrome toggle makes downloads less distracting on your computer Chrome's 2023 redesign is coming together with new hover animation The Pixel's Live Translate feature could soon come to Google Chrome on desktop Google's got plenty of Chrome love to go around with new features for iOS Google's got plenty of Chrome love to go around with new features for iOS.NOTE: The release notes for M100 to M103 were not sent out.NOTE: The release notes for M106 and M107 were not sent out.To find a branch associated with a particular release, refer to the list of branches. To find out the current release and schedule, refer to the chromium dashboard. Some manual filtering is done to remove issues associated with build changes, tests and trivial code changes.

third_party/blink/renderer/modules/breakout_box.

third_party/blink/renderer/modules/webrtc.

third_party/blink/renderer/modules/mediastream/.

third_party/blink/renderer/platform/p2p/.

third_party/blink/renderer/platform/peerconnection/.

third_party/blink/renderer/modules/peerconnection/.

For Chromium, the following directories are considered: This should be done between the branch date and the release date in order to account for “late” merges.įor WebRTC, all files in the repository are taken into account. That have been marked as Fixed or Verified.

Release notes are generated by taking the git log between the respective release branches using git log branch-heads/5672.branch-heads/5735Īnd finding monorail issues associated with the BUG= line extracted from the git log as grep -i 'Bug' | sed 's/^ *//g' | grep -i ^Bug | sort -n | uniq The release notes are posted to the discuss-webrtc mailing list before the release. This document contains pointers to the WebRTC release notes for each Chrome release.