Google Declares Chrome 25 As Stable
Days after Mozilla released Firefox 19, Google has pushed its Chrome 25 web-browser into their stable channel.
The most notable additions to Google Chrome 25 is proper support for the JavaScript Web Speech API, improved WebGL error handling, improvements in managing/securing browser extensions, better support for HTML5 time/date inputs, and lots of other new developer features. There's also been a number of security/bug-fixes that were taken care of with Chrome 25.
The Web Speech API is about speech synthesis and recognition for JavaScript-based web applications. Per the W3.org API specification, "[the Web Speech API] enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives."
Google noted that many of the issues they spotted and resolved for Chrome 25 were discovered through the use of AddressSanitizer, a feature of LLVM that's now being ported to GCC. Google is responsible for the AddressSanitizer work as well as ThreadSanitizer in these open-source compilers.
More details on Chrome 25 can be found from the Chrome 25 blog announcement.
The most notable additions to Google Chrome 25 is proper support for the JavaScript Web Speech API, improved WebGL error handling, improvements in managing/securing browser extensions, better support for HTML5 time/date inputs, and lots of other new developer features. There's also been a number of security/bug-fixes that were taken care of with Chrome 25.
The Web Speech API is about speech synthesis and recognition for JavaScript-based web applications. Per the W3.org API specification, "[the Web Speech API] enables developers to use scripting to generate text-to-speech output and to use speech recognition as an input for forms, continuous dictation and control. The JavaScript API allows web pages to control activation and timing and to handle results and alternatives."
Google noted that many of the issues they spotted and resolved for Chrome 25 were discovered through the use of AddressSanitizer, a feature of LLVM that's now being ported to GCC. Google is responsible for the AddressSanitizer work as well as ThreadSanitizer in these open-source compilers.
More details on Chrome 25 can be found from the Chrome 25 blog announcement.
3 Comments