Chrome will make it more difficult to block navigation incognito

The problem is related to the "FileSystem" API of Chrome. When a browser is in incognito mode, the API is disabled. when third party sites can not access the API, it is an Incognito red flag.

In the future, when third-party sites request the FileSystem API, Chrome will create a temporary virtual file system in the RAM of a computer. Third party sites will not know which Chrome system is running and will not be able to detect or block Incognito web browsers. This also makes it easy for Chrome to delete this temporary file system when the browser is closed.

However, as The edge points out that this could be a temporary solution until the FileSystem API is completely removed, which can happen if Google determines that the API is only revealing private browsing users.

For the moment, this workaround will first appear as an experimental feature in the Canary version of Chrome 74. Hopefully, this feature will be standard on Chrome 76.