Chrome version: 125, 124, 123, 122, 121, 120, 119, 118, 117, 116, 115, 114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0
This release of Chrome had 6 new features.
The Cache API allow authors to fully and conveniently manage their content caches for offline use. An origin can have multiple, named Cache objects which are accessible via workers and document scripts. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/Cachehttps://developer.mozilla.org/en-US/docs/Web/API/CacheStorage
Samples: https://github.com/GoogleChrome/samples/blob/gh-pages/service-worker/README.md
An evolution of the Content Security Policy specification, allowing developers to create a whitelist of sources of trusted content, and instructing the browser to only execute or render resources from those sources. #
This feature was specified in this Spec.
ServiceWorkers (formerly Navigation Controllers) are a new system that provides event-driven scripts that run independent of web pages. They are similar to SharedWorkers except that their lifetime is different and they have access to domain-wide events such as network fetches. Use cases: offline, reducing perceived page load latency and will eventually power notification/push/sync/... use cases. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorker_APIhttp://www.html5rocks.com/en/tutorials/service-worker/introduction/http://jakearchibald.com/2014/using-serviceworker-today/
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/service-workerhttps://github.com/jakearchibald/trained-to-thrill
The HRTF panner uses significant memory for the responses and requires a fair amount of processing to implement. For low-end mobile devices, this can be an issue. Since the default panner model is HRTF, the creation of the panner can cause the responses to be loaded. The default has been changed to equalpower, which doesn't consume significant memory and is much less intensive in processing power. #
This feature was specified in this Spec.
minlength attribute declares a lower bound on the number of characters a user can input. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input#attr-minlengthhttps://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea#attr-minlength
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/report-validity
reportValidity() invokes built-in form validation UI programatically. #
This feature was specified in this Spec.
Docs: https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/reportValidity
Samples: https://github.com/GoogleChrome/samples/tree/gh-pages/report-validity
This release of Chrome had 0 new origin trials.
This release of Chrome had 0 are available behind a flag.
To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:
Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.
Chrome currently has a process for deprecations and removals of API's, essentially:
You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.
This release of Chrome had 0 features deprecated.
This release of Chrome had 0 features removed.