Although Chrome has already opened open tabs on each of the tabs, Incognito mode takes additional steps to protect your privacy. Cookies and other data stored locally are erased at the end of the session and the history is never saved. However, sites could use known workarounds to determine if they were operating in private browsing mode, and Google finally solves them.
The FileSystem API was introduced by Google in 2010 and allows sites to create their own virtual file systems for reading and writing local data. The feature has never been widely used and Chrome and Opera remain the only mainstream browsers to support it. Chrome disables access to the FileSystem API in the incognito sessions, so sites can check if the API is disabled to determine if they are running in open mode. private navigation.
According to a series of commitments to Chromium Gerrit, Google modifies the API to work under Incognito, by storing the files in the RAM. According to a design document obtained by 9to5Google, the company hopes to completely remove the API:
"In the absence of adoption of the FileSystem API by other browser vendors, it seems that only websites detect incognito mode.While making this more difficult, we hope that the overall use of the API decreases to the point that we can depreciate and delete it. "
In short, if a site you visit can determine if you are in Incognito mode, it will no longer be possible.