Firefox tried to reduce notification spam, the Guardian gets a new rendering layer and GOV.UK Prototype Kit gets a new release.
Fortnightly internal newsletters
Firefox starts blocking audio and video by default, Android users get to choose their browser after being fined by the European Commission.
Chrome gets an urgent security update, WebAuthn becomes officially recommended and new Edge looks like Chrome.
Microsoft says Internet Explorer as your default browser is bad and .dev domains coming very too.
Play store now accepts PWAs, Firefox 66 mutes the web, Do Not Track is dead and so is IE10.
Windows 10 mobile end-of-life announced, Priority hints spec released and the US courts can force WCAG 2.0 compliancy.
GitHub announces unlimited private repos and GOV.UK Frontend gets a new release with 2 new components.
Microsoft is replacing Edge with a Chromium based browser, moving away from the EdgeHTML rendering engine.
HTTP/3 becomes official and Chrome 71 will start to crack-down on sites that show abusive behaviors.
A new version of GOV.UK Frontend and the Prototype kit are released, Google launches reCAPTCHA v3.
RawGit is shutting down, Firefox gets WebP support and GitHub adds a new feature called actions.
Chrome clamps down on extension security, Flexbox is everywhere and MDN looks for backing from users.
GOV.UK Frontend v2.0.0 is released, AMP moves towards open governance and Microsoft is up to its old tricks again.
Chrome can disable JS on slow networks, AMP is taking over the web and needs to be stopped and Chrome turns 10 years old.
China releases Google Chrome, NPM ups its security and native lazy loading comes to the web.
Creative coding in 13KB of JS, Chrome 69 goes beta and Let's Encrypt is trusted by all major root programmes.
Chrome 68 released to stable with HTTP pages marked as insecure by default!
Npm module eslint-scope is compramised, Chrome ^& is released and CSS-nesting is becoming a proposal.
Microsoft aquires GitHub, Chrome 67 hits stable and WCAG 2.1 becomes a W3C recommendation.
Mozilla publish a health report, Sublime gets a new release and a number of banks forget to check their changes with a11y users.
Node 10 released, Chrome 66 hits stable and Github depreciates IE in 3 months.
Firefox nightly gets a new tool, the Accessibility Inspector and the big three browser vendors back the new Web Authentication API.
Mozilla tackling Facebook tracking, Sensor APIs are now W3C Candidate Recommendations and MDN is bringing interactive examples to their web docs.
The WWW turned 29 and Let's Encrypt adds wildcard certificate support.
Discussions on security of 3rd party CSS, Flash is nearly dead and PhantomJS stops development.
Progressive web apps landed in Edge, Google is adding AMP support to emails and Chrome enables ad-blocking.
Service workers as they land in macOS Safari and iOS Safari, Google Chrome is to implement image lazy loading natively, Web Content Accessibility Guidelines (WCAG) 2.1 is now a Candidate Recommendation.
The AMP team are making changes to how AMP URL's work, Google Chrome autoplay policies will change in January, TC39 recommends the use of semicolons to stop future ASI issues.
Chrome to start blocking non-standard ads from Feb 15th, security issues with Intel CPU's and is Chrome becoming the new IE6?
A huge security issue was recently tweeted, Google's AI built an AI that outperforms any created by humans, Google is shutting down Chrome Apps.
Firefox 57 (Quantum) has been released, WebAssembly support is now shipping in all major browsers and OWASP top 10 security risks for 2017.
Netflix removed client-side rendering using React, Samsung Internet 6.2 released, CSS Grid specifications landed with the release of Edge 16.
Chrome to stop in-browser cryptocurrency miners, Firebug has now reached end-of-life, collaboration with Microsoft & Google around the MDN Web Docs.
Edge is coming to iOS soon, Chrome 62 brings a whole bunch of new features to play with in the DevTools.
World Wide Web Consortium abandons consensus, standardizes DRM with 58.4% support, React relicensed under MIT.
Wordpress are to stop using React, Advertisers don’t like Safari's the new cookie blocking and auto-play to be disabled in Chrome 64.