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.
Last week, Mozilla hinted at Firefox Developer Edition, a version made "by developers, for developers." This special version is part of a celebration of the 10 year anniversary of the release of Firefox 1.0. But, in the days preceding the release, the company has gone uncharacteristically quiet.
Bootstrap 3.3.0 was announced last week, along with a set of upcoming changes in Boostrap 4 alpha. One of the biggest changes coming soon is removal of support for IE8.
After gestating for more than a year on GitHub, the project Streams has now been adopted by WHATWG in an effort to standardize a web streaming API. The project is led by Domenic Denicola, the man that started the work on Promises, currently part of the upcoming ECMAScript 6.
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.