Google Chrome developers have proposed adding support for a new HTML tag to allow web developers from ensuring its users aren’t tracked by third party cookies.
All current web browsers allow third-party iframes to communicate with the website that has embedded them. This is something that unscrupulous web developers often exploit to invade the privacy of the visitors and track their online movements.
While ferrying data across websites through an iframe was permissible earlier, with the move towards disabling third-party cookies altogether, browser developers are looking for means to restrict an iframe from sending data back to the original website that embedded it.
We're looking at how our readers use VPN for a forthcoming in-depth report. We'd love to hear your thoughts in the survey below. It won't take more than 60 seconds of your time.
- Check our list of the best VPN services
- We’ve also compiled a list of the best options for anonymous web browsing
- These are the best proxy service providers
Google’s answer is a new embedded iframe called Fenced Frame, which it has proposed as a means to isolate user data and prevent it from being read by other web pages.
Google describes Fenced Frames as a new form of an embedded document that helps erect a boundary between the embedding page and the cross-site embedded document.
It contends that this new tag will ensure that two websites will not be able to share user data, in essence shielding users from all manners of privacy abuse, including tracking.
Chrome developers further limit Fenced Frames by not giving the tags access to a browser’s storage areas including the cache, and the localStorage object, by default.
Although Google suggests that the new tags are still a prototype and are not in active development, reportedly they’ve been added to recent test builds of Chrome.
- We’ve built a list of the best business VPN solutions on the market