Google is going to make Pointer Events the main event type in Chrome, joining ranks with Microsoft, Firefox and leaving out Apple.
Facebook has open sourced Stetho, an Android debugging bridge enabling developers to debug their apps using Chrome DevTools.
The modern.IE Platform Status indicates that now asm.js is in Development. According to Microsoft, the Chakra engine in Windows 10 will support asm.js, and Microsoft has been collaborating with Mozilla to implement it faster. Chrome is going to support it via TurboFan, a new optimizing compiler for V8.
Google has made Android WebView available as a standalone application for developers willing to test it.
The SFHTML5 group recently had a meeting discussing HTML5 technologies for creating virtual reality experiences – WebGL, WebVR, Three.js, GLAM –, and the current development status for implementing support for them in Firefox and Chrome. The idea is to bring the entire web into the VR experience.
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?