- Online privacy is something that continues to draw attention making it an important factor when deciding which browser to use.
- An entry for many web developers to invade the users' privacy has been through third-party iframes.
- Chrome developers have worked on adding an HTML tag that will prevent an iframe from sending private data to other websites.
- It aims at creating a boundary between the embedding page and the cross-embedded document.
Online privacy continues to be of paramount importance especially nowadays when more and more creative ways of attacks and viruses are taking place.
With the current updates, Chrome has been aligned with more web standards than any of the available browsers out there, making it a perfect choice for users.
On every update that has been launched, Chrome also benefited from reinforcements in the security and privacy area.
Fenced Frame privacy feature
As of right now all current browsers allow third-party iframes to communicate with the website that has embedded them which can be dangerous.
More than once we have seen proof of how web developers have used such occasions in order to invade users’ privacy by tracking their online actions.
In order to try and solve this issue, Chrome developers have proposed to add support for a new HTML tag that will allow them to ensure that their users will not be tracked by third-party cookies.
The fenced frame enforces a boundary between the embedding page and the cross-site embedded document such that user data visible to the two sites is not able to be joined together.
By completely disabling third-party cookies, browser developers will restrict an iframe from sending data back to the original website.
The new embedded iframe will be called Fenced Frame and it’s expected to isolate all user data and restrict it from being read by other web pages.
Once third-party cookies have been removed, such documents should not be allowed to communicate with their embedders, else they will be able to join their cross-site user identifiers with the embedder’s, which would allow for user tracking. This explainer proposes a new form of embedded document, called a fenced frame, that these new APIs can use to isolate themselves from their embedders, preventing cross-site recognition.
In other words, this new tag will not permit that a users data is shared between two websites and it will protect them from any form of privacy abuse, tracking included.
According to Google, the new tags are not yet in active development although it seems that they have been added to recent test builds of Chrome.
As always, we welcome your thoughts, so don;t hesitate to leave us a comment in the dedicated section below.