“Still, we appreciate that it will take time to transition away from NPAPI, so we will be rolling out this change in stages.” “Based on anonymous Chrome usage data, we estimate that only six NPAPI plug-ins were used by more than 5 percent of users in the last month,” wrote Justin Schuh, security engineer at Google, in a blog post. While users can still turn it on if they need to, Google has already stated that it intends to eliminate its support for NPAPI at some point in 2015. In Chrome 42, this API is turned off by default. Plugins such as Java and Silverlight use an API called NPAPI, or Netscape Plugin API. Google may also be attempting to move away from traditional plugins through Chrome 42.
The thought of multiple pop-up notifications may seem obnoxious to some, but Google notes that developers will need to ask for permission to use Push API. Chrome 42 includes the new Push API and Notifications API, which are designed to provide notifications to users after they’ve left a specific website. Google went under the hood to enhance stability and performance as well. However, the introduction of Chrome 42 to the stable channel wasn’t all about bugs and fixes. It is continuing to encourage users to report any underlying issues that they come across on its Code site. Google noted that many of the other bugs were detected using AddressSanitizer or MemorySanitizer. “We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel,” wrote Google’s Alex Mineer, in the blog post. In a blog post, Google laid out several improvements made to the browser, including 45 security fixes, many of which were submitted by external researchers. Google announced the release of Chrome 42 to the stable channel on April 14, and the update is now available on Windows, Mac and Linux.
0 kommentar(er)
