Incognito Mode in Google Chrome browser protects your privacy by deleting cookies, and locally stored data and does not save a record of your history. Little do people know that due to a flaw in Chrome, developers can easily identify whether you are using incognito mode or not. Google has finally taken this into consideration and has been working on to fix it.
In 2010, Google introduced FileSystem API which let sites create virtual file systems to read and write local data. This function was only supported by Chrome and Opera mainly. In Incognito mode, chrome disabled access to FileSystem API, enabling sites to see whether the API is disabled and users are in Incognito mode.
As per the series of commits to Chromium Gerrit, after years of knowing the existence of this issue, Google is bringing a solution for it. Chrome will create a virtual file system using RAM, ensuring that it will be deleted when the session is over, making it hard to know whether the user is in incognito mode or not. According to internal design document, after thus protection, FileSystem API will be removed.
This Incognito mode detection prevention feature will be introduced in Chrome 74, behind a flag. Whereas, it will be available by default in Chrome 76. For now, you will be able to disguise incognito mode in Chrome Canary builds using flag #enable-filesystem-in-incognito.
In 2010, Google introduced FileSystem API which let sites create virtual file systems to read and write local data. This function was only supported by Chrome and Opera mainly. In Incognito mode, chrome disabled access to FileSystem API, enabling sites to see whether the API is disabled and users are in Incognito mode.
As per the series of commits to Chromium Gerrit, after years of knowing the existence of this issue, Google is bringing a solution for it. Chrome will create a virtual file system using RAM, ensuring that it will be deleted when the session is over, making it hard to know whether the user is in incognito mode or not. According to internal design document, after thus protection, FileSystem API will be removed.
This Incognito mode detection prevention feature will be introduced in Chrome 74, behind a flag. Whereas, it will be available by default in Chrome 76. For now, you will be able to disguise incognito mode in Chrome Canary builds using flag #enable-filesystem-in-incognito.
