Google Chrome 56, currently in Beta stage, will show a distinctive and visible warning text when users navigate to pages hosted on HTTP that contain sensitive form elements such as fields for password or credit card data input.
The warning, pictured above, was announced in September, but users who download and install Chrome 56 Beta can now experience it first hand.
According to the Google team, the warning doesn't show on all HTTP websites, but only on those with password fields and payment forms.
Chrome 56 is scheduled to launch at the start of January 2017. Chrome will join Firefox, as the second browser that shows some sort of warnings for insecure operations carried out via HTTP. Firefox has been showing warnings for login forms on HTTP pages since version 44 and is about to add more "in your face" warnings starting with Firefox 52.
Besides the support for more aggressive alerts for insecure operations, Chrome 56 will also be the first Chrome version to support the W3C Web Bluetooth API, a technology that lets websites interact with Bluetooth-enabled devices in your home (after the user grants it permission, of course).
The Web Bluetooth API has come under fire recently after privacy expert Lukasz Olejnik has criticized the W3C for some of its features, which he claimed allowed an attacker to spy on users.
Last but not least, developers will love the new CSS "position: sticky" property, which they can now apply to make elements stick to the top of their parent container, or the viewport (screen).
CSS "position: sticky" simplifies and automates this process, which can now be left to the browser, instead of having to write code for it yourself.