The service worker browser feature holds promise for developers looking to make their web apps feel more like native apps. Running in the background and without user interaction, service workers enable advanced scenarios such as offline functionality, cache, background sync, geofencing, and push notifications.
Google's Chrome team has released the stable version of Chrome 39: with updates including the Web Application Manifest specification, Beacon API, and support for ES6 generators.
Google has added support for the
Mozilla has implemented the protocol adapters that enable remote debugging in Chrome for desktop or Android and Safari/iOS. They are to be integrated into WebIDE.
Google Chrome no longer supports window.showModalDialog, breaking several enterprise apps such as OWA, EAC, SAP, and others.
Google's Chrome web browser team has announced a schedule to deprecate support for how the browser handles HTTPS certificates using SHA-1 signatures. Over the next 6 months the browser will utilize increasingly noticeable warnings for sites that still use SHA-1.
The first stable ORTC (Object RTC) specification is out. The questions is how is it going to impact WebRTC?
Google released Chrome 36 for Windows, Mac, Linux and Android which includes some additions and improvements as well as various bug fixes and performance tweaks.
The Status.IE project provides compatibility information for 4 major web browsers, allowing developers to see which features are available based on the browsers they need to support. Microsoft has open-sourced both the code serving the project and the data it offers, making it easy for developers to further their own development projects.
QUIC (Quick UDP Internet Connections, pronounced 'quick') is a multiplexing transport protocol running over UDP with the main goal to have 0-RTT connectivity overhead.
Developer can now deploy Chrome apps on Android and iOS with Apache Cordova 3.3.0.