The Google Chrome development team has launched the official version of Google Chrome v81, which was originally released in March but has been delayed due to the epidemic. This update includes 32 security fixes.
The highlight of this update is that Google began to support the Web NFC standard, which is an API that can be used to call NFC sensors based on browsers and web pages.
For example, on a smartphone or tablet that supports NFC sensors, the web page can call the API interface to directly read the content contained in the surrounding NFC tags.
However, this is also the first time that Google Chrome supports this standard. Web developers can pay attention to and test this feature in advance. At present, this feature is not enabled by default. Developers who need to test can open it through relevant experimental options, and subsequent versions will only be enabled by default.
Based on security considerations, Google Chrome is gradually removing support for mixed content. The so-called mixed content refers to loading HTTP protocol content in HTTPS.
Although some websites have deployed encryption, some resources called by them, such as pictures, audio, and video or scripts and style sheets, are still transmitted using the clear text protocol.
Google ’s goal is to deploy full-site encryption on all websites, but Google is concerned that sudden restrictions on mixed content will cause much content on the Internet to fail to load properly.
So Google adopted a step-by-step strategy, and the Chrome v81 version has been implemented to the third step and the last step: that is, to restrict HTTP content loading.
Starting from this version, all HTTP content loaded in the HTTPS web page will be blocked, whether it is pictures, scripts, style sheets, or audio and video.