Microsoft has provided new information on the reasoning behind the switch to a brand new rendering engine for Project Spartan, the web browser shipping with Windows 10. The new engine is a fork of Trident and eliminates swathes of code that have been in place for 20 years.
The World Wide Web Consortium (W3C) has published the Pointer Events standard as a recommendation for wide adoption, but its future is in doubt as Apple and Google are refusing to implement it.
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.
Microsoft has released details of its rumoured Spartan browser project, and confirms a move towards standards used by other, more modern, browsers.
A team of former Opera developers along with their ex-CEO Jon von Tetzchner have created a new browser called Vivaldi.
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 Chromium team announced back in August that Google is no longer working on implementing Pointer Events in Chrome in order to focus on Touch Events. Now they have given control to the Pointer Events polyfill library to jQuery which is hoping to “drive developer adoption of this unified event system” and eventually see “all browsers implement this standard natively.”
Mark Nottingham, chair of the HTTP Working Group, asks the question What is the Web? As he mentions, this simple question has some complex and perhaps unexpected answers depending upon your perspective. A common approach would be to say that it has to be rooted in the Web browser, but that has some interesting consequences, not all of which are useful for non-browser stakeholders.
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.
Mozilla has this week released Firefox 34, with notable features including SSLv3 disabled by default, WebIDE, and the implementation of ECMAScript 6 WeakSet.
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.
Microsoft has released secruity improvements to Internet Explorer, fixing a vulnerablity that could allow an attacker to take control of a user's system. But according to Robert Freeman, manager of IBM X-Force Research, the issue was reported to Microsoft with a working proof-of-concept back in May 2014 -- and the issue is far older.