Menu

Browser News

A Business Case for Dropping Internet Explorer

October 28th, 2019

The distance between Internet Explorer (IE) 11 and every other major browser is an increasingly gaping chasm. Adding support for a technologically obsolete browser adds an inordinate amount of time and frustration to development. Testing becomes onerous. Bug-fixing looms large. Developers have wanted to abandon IE for years, but is it now financially prudent to…

The Landscape of Cross-Platform App Development

October 25th, 2019

I don’t track this stuff very well, but I get it. If you want a native app for Android and iOS, it sure would be nice to only have to write it once rather than two very different languages. Roughly double your reach without doubling the work. More and more of these things are reaching…

Weekly Platform News: WebAPK Limited to Chrome, Discernible Focus Rectangles, Modal Window API

October 24th, 2019

In this week’s roundup: “Add to home screen” has different meanings in Android, Chrome and Edge add some pop to focus rectangles on form inputs, and how third-party sites may be coming to a modal near you. Let’s get into the news. WebAPKs are not available to Firefox on Android On Android, both Chrome and…

Automatically lazy-loading offscreen images & iframes for Lite mode users

October 24th, 2019

In Chrome 76, we introduced native lazy-loading for images and iframes via the `loading` attribute – a developer opt-in. In Chrome 77, Chrome Android users with  Lite Mode (Data Saver) enabled will benefit from native lazy-loading of images and iframes automatically. Lite mode has allowed Chrome to reduce users’ data usage by up to 60…

Developers: Get Ready for New SameSite=None; Secure Cookie Settings

October 23rd, 2019

In May, Chrome announced a secure-by-default model for cookies, enabled by a new cookie classification system (spec). This initiative is part of our ongoing effort to improve privacy and security across the web. Chrome plans to implement the new model with Chrome 80 on February 2020. Mozilla and Microsoft have also indicated an intent to…

Recent Site Isolation improvements

October 17th, 2019

In July 2018 we launched Site Isolation in Chrome as a way to secure desktop browsers against the risk of side-channel attacks like Spectre. We recently published a USENIX Security conference paper highlighting the benefits of this launch. Today, we are pleased to announce further improvements we’ve rolled out in Chrome 77: Chrome for Android…

DM Verity Algorithm Change

October 16th, 2019

One of the foundational security features of Chromebooks is Verified Boot, which protects our users from potentially malicious software being run on their devices. The last chain of verification in this process is to validate the integrity of the root file system (rootfs). This blog post describes a recent enhancement to this rootfs validation to…

Weekly Platform News: Tracking via Web Storage, First Input Delay, Navigating by Headings

October 3rd, 2019

In this week’s roundup, Safari takes on cross-site tracking, the delay between load and user interaction is greater on mobile, and a new survey says headings are a popular way for screen readers to navigate a webpage. Let’s get into the news. Safari’s tracking prevention limits web storage Some social networks and other websites that…

No More Mixed Messages About HTTPS

October 3rd, 2019

Today we’re announcing that Chrome will gradually start ensuring that https:// pages can only load secure https:// subresources. In a series of steps outlined below, we’ll start blocking mixed content (insecure http:// subresources on https:// pages) by default. This change will improve user privacy and security on the web, and present a clearer browser security…

Chrome UI for Deprecating Legacy TLS Versions

October 1st, 2019

Last October we announced our plans to remove support for TLS 1.0 and 1.1 in Chrome 81. In this post, we’re announcing a pre-removal phase in which we’ll introduce a gentler warning UI, and previewing the UI that we’ll use to block TLS 1.0 and 1.1 in Chrome 81. Site administrators should immediately enable TLS…