Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
The Boston Globe detects Private tabs, and raises a paywall.
window.webkitRequestFileSystem(0, 1, function() {
// User is assumed to be in a normal tab
}, function(n) {
// User is assumed to be in a private/incognito tab
});
When the user is thought to be in a Private tab, the <body> is given overflow: hidden to prevent scrolling, and a div.gip__modal element is appended to the body.
Platform (Win7, 8, 10? macOS? Linux distro?):
Desktop
Brave Version (revision SHA):
Steps to reproduce:
Actual result:
Note paywall
Expected result:
No paywall
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes
Is this an issue in the currently released version?
Yes
Can this issue be consistently reproduced?
Yes
Supposedly this is the Chrome bug, but I can't access it:
https://bugs.chromium.org/p/chromium/issues/detail?id=93417
(Source: https://bugs.chromium.org/p/chromium/issues/detail?id=663727 )
Related with https://github.com/brave/browser-laptop/issues/10269 ?
@luixxiul I don't think this is related to #10269. That issue is more about fingerprinting, while this one is merely identifying whether the user is in a Private tab, and then blocking them from certain content.
~cc: @lukemulks in case he may know what to look for when investigating~
@bsclifton At the time, they were using the following to detect private tabs:
window.webkitRequestFileSystem(0, 1, function() {
// User is assumed to be in a normal tab
}, function(n) {
// User is assumed to be in a private/incognito tab
});
@jonathansampson ah thanks- I totally missed that in the original post 馃槃
Can confirm this is fixed on both the latest Brave Desktop release and Brave for Android.
Most helpful comment
Can confirm this is fixed on both the latest Brave Desktop release and Brave for Android.