Chrome 56 for Mac and other platforms has entered Google’s beta channel. When released to the general public, the browser will bring native support for the FLAC audio codec within the browser and other perks. This should come in handy because macOS does not support the FLAC file format out of the box so users often must use a third-party converter or video player to play these files. With Chrome 56, Mac users will be able to play FLAC-encoded audio files embedded in web pages or local files drag and dropped onto the browser window.

Other enhancements are part of Chrome 56 for for Android, Chrome OS, Linux, Mac and Windows.

For instance, there will be a brand new “Not Secure” warning for HTTP password and credit card pages. Google’s browser has always indicated connection security with a green icon in the address bar for secure HTTPS pages, but Chrome 56 will now mark regular HTTP pages that collect passwords or credit cards as non-secure.

The search company claims that this feature, which will roll out gradually over the next few weeks, is “part of a long-term plan to mark all HTTP sites as non-secure.”

In other words, website developers will need to secure their traffic with HTTPS and follow general security guidelines unless they’re OK with Chrome labeling their websites as insecure.

Newly added support for the web Bluetooth protocol will let Chrome 56 connect to and interact with Bluetooth Low Energy devices such as printers, LED displays, heart rate monitors and more via the Web Bluetooth API on Android, Chrome OS and Mac.

This feature can be combined with physical Bluetooth beacons to discover and control nearby devices. Other new features, enhancements and tidbits in this release of Chrome 56 are listed in Google’s blog post linked below.

Source: Google

  • When iDB will use HTTPS?

    • 5723alex .

      Chrome Version 56.0.2924.59 beta (64-bit) : Your connection to this site is not secure…

  • chjode

    The “everything must be HTTPS” campaign is silly. If I’m not submitting user data or financial information, who cares?

    • It’s not silly at all. Without HTTPS you have no guarantee that the content you’re viewing is genuine. A government could modify news sites delivered over HTTP to spread propaganda or download links could be compromised. Just because you aren’t submitting user data or financial information don’t think you aren’t at risk.

    • Nolan I.

      HTTPS is great when it works. It actually messes up my internet in places like at my school, where a seriously flawed (by design) web filter forcibly overwrites the HTTPS certificates with its own.

      Chrome does not like this one bit, insisting that I don’t even set foot on the website. For non-HSTS websites you can bypass it, but I ended up using a command line flag to always ignore certificate errors. (Or I just use a VPN, but still somehow the certificates end up borked.)

      It’s annoying that I now think of HTTPS as a nuisance than a security feature, and it is desensitizing me to the security warnings…

  • Thank you very muck