IndexedDB does not function in private browsing mode
Categories
(Core :: Storage: IndexedDB, defect, P3)
Tracking
()
Webcompat Priority | ? |
People
(Reporter: bugs, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Whiteboard: [DevRel:P1])
Attachments
(1 file, 2 obsolete files)
19.65 KB,
patch
|
janv
:
feedback+
|
Details | Diff | Splinter Review |
Comment 1•12 years ago
|
||
Comment 4•12 years ago
|
||
Comment 6•12 years ago
|
||
Comment 8•12 years ago
|
||
Reporter | ||
Comment 11•12 years ago
|
||
Comment 12•12 years ago
|
||
Reporter | ||
Comment 13•12 years ago
|
||
Comment 14•12 years ago
|
||
Updated•12 years ago
|
Comment 16•12 years ago
|
||
Comment 17•12 years ago
|
||
Comment 18•11 years ago
|
||
Comment 19•11 years ago
|
||
Reporter | ||
Comment 20•11 years ago
|
||
Comment 21•10 years ago
|
||
Updated•10 years ago
|
Reporter | ||
Comment 22•10 years ago
|
||
Comment 24•9 years ago
|
||
Comment 25•9 years ago
|
||
Comment 26•9 years ago
|
||
Comment 27•9 years ago
|
||
Comment 28•9 years ago
|
||
Comment 29•9 years ago
|
||
Comment 31•9 years ago
|
||
Comment 32•9 years ago
|
||
Comment 33•9 years ago
|
||
Comment 34•9 years ago
|
||
Comment 35•9 years ago
|
||
Comment 36•9 years ago
|
||
Comment 37•9 years ago
|
||
Comment 38•9 years ago
|
||
Updated•9 years ago
|
Comment 39•9 years ago
|
||
Updated•9 years ago
|
Updated•9 years ago
|
Comment 40•9 years ago
|
||
Comment 41•8 years ago
|
||
Comment 42•8 years ago
|
||
Comment 43•8 years ago
|
||
Comment 44•8 years ago
|
||
Comment 45•8 years ago
|
||
Comment 46•8 years ago
|
||
Comment 47•8 years ago
|
||
Comment 48•8 years ago
|
||
Comment 49•8 years ago
|
||
Comment 50•8 years ago
|
||
Comment 51•8 years ago
|
||
Comment 52•8 years ago
|
||
Comment 53•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Comment 54•8 years ago
|
||
Comment 55•8 years ago
|
||
Comment 56•8 years ago
|
||
Comment 57•8 years ago
|
||
Comment hidden (advocacy) |
Comment 59•7 years ago
|
||
Comment 60•7 years ago
|
||
Comment 61•7 years ago
|
||
Comment 62•7 years ago
|
||
Comment 63•7 years ago
|
||
Updated•7 years ago
|
Comment 64•7 years ago
|
||
Comment 66•7 years ago
|
||
Updated•7 years ago
|
Comment 67•7 years ago
|
||
Comment 68•7 years ago
|
||
Comment 69•7 years ago
|
||
Updated•7 years ago
|
Comment 70•7 years ago
|
||
Comment 71•6 years ago
|
||
Comment 72•6 years ago
|
||
Updated•6 years ago
|
Comment 73•6 years ago
|
||
Comment 74•6 years ago
|
||
Comment 75•6 years ago
|
||
latimes.com also does something similar, using https://eb.trbas.com/tronc/latimesarcprod/Bootstrap.js. The user sees https://imgur.com/iGyOOuN.
Comment 76•6 years ago
•
|
||
Stackoverflow answered a question in late 2016 about how, specifically, to fingerprint Private Browsing users for whatever reason:
Which spawned this gist, that is being maintained actively to this day:
https://gist.github.com/jherax/a81c8c132d09cc354a0e2cb911841ff1#file-is-private-mode-js-L32
// Firefox
if ('MozAppearance' in document.documentElement.style) {
const db = indexedDB.open('test');
db.onerror = on;
db.onsuccess = off;
return void 0;
}
While the SO question implies that it's to require private browsing mode, sites that depend on user tracking revenue in the wild are using the same logic to refuse service to Private Browsing users.
Comment 77•6 years ago
|
||
https://ghacksuserjs.github.io/TorZillaPrint/TorZillaPrint.html .. see "private window" in the first section on screen
// PB Mode
try {
var db = indexedDB.open("IsPBMode");
db.onerror = function() {dom.IsPBMode = "true";};
db.onsuccess = function() {dom.IsPBMode = "false";};
}
catch(err) {
dom.IsPBMode = "unknown";
}
unknown will happen if you have cookies blocked. The test site is for FF and TB only. But if you wanted to make it universal you would just wrap it in any Firefox feature detection such as
if (isNaN(window.mozPaintCount) === false){ console.log("Firefox")};
if (isNaN(window.mozInnerScreenX) === false){ console.log("Firefox")};
if (isNaN(window.window.scrollMaxX) === false){ console.log("Firefox")};
if (navigator.oscpu == undefined){} else { console.log("Firefox")};
Comment 78•6 years ago
|
||
NYTimes is testing the waters with this as well: http://www.niemanlab.org/2019/02/your-favorite-way-to-get-around-the-new-york-times-paywall-might-be-about-to-go-away/
Comment 80•6 years ago
|
||
Google is testing a patch to the analog to IndexedDB (the FileSystem API) to prevent targeting of users using private browsing in Chrome, FYI: https://9to5google.com/2019/02/15/google-chrome-detect-incognito/
Comment hidden (advocacy) |
Comment hidden (advocacy) |
Comment 86•6 years ago
|
||
Per bug 1506680, many newspapers are using this to trigger paywalls - NYTimes, WashingtonPost, Baltimore Sun, Boston Globe, and others.
Comment hidden (me-too) |
Comment hidden (advocacy) |
Comment 89•6 years ago
|
||
For the folks who keep commenting here, we are aware of the importance of this bug and of the wide impact of it on many different websites. More comments of this sort aren't helpful.
We are hoping to fix this bug in the next few months, before the end of the year. Please remain patient, thanks!
Comment hidden (advocacy) |
Comment hidden (me-too) |
Updated•6 years ago
|
Comment 92•6 years ago
•
|
||
(In reply to Mark Baysinger from comment #90)
the priority of this bug is still P3, which according to the wiki means: "This isn't a bad idea, and maybe we'll want to implement it at some point in the future, but it's not near-term roadmap material. Some core Bugzilla developer may work on it."
Actually, the wiki page you're referring to isn't applicable here. It's not very clear, but it's actually describing priorities for bugs/problems with the bugzilla product itself. (note "Some...Bugzilla developer", i.e. someone who works on Bugzilla-as-a-product.)
The P1-P5 semantics for bugs in Firefox are semi-defined in a table here: https://mozilla.github.io/bug-handling/triage-bugzilla
Basically P1 and P2 are reserved for extremely-severe bugs that must be fixed within 1-2 releases (e.g. showstopper bugs), whereas P3 is a wide category for bugs that we also want to fix but not necessarily in the immediate next release. Most bug fixes that land are for P3 bugs.
Anyhow, this is all off-topic, and this bug now has comments restricted so that it can hopefully still remain useful for implementation discussion (without having to wade through a backlog of 100+ comments) once someone starts working on it.
Comment 99•5 years ago
|
||
QuotaManager storage v2 will use UUIDs for origin directory names and keep the mapping between origin and origin directory in the memory and a database. For private browsing, we would keep it in memory only.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 102•5 years ago
|
||
Adding support for IndexedDB in private browsing mode is now tracked in Bug 1639542.
Updated•5 years ago
|
Description
•