Expose quota-manager APIs in PrivateBrowsing
Categories
(Core :: Storage: Quota Manager, enhancement, P2)
Tracking
()
People
(Reporter: baku, Assigned: baku)
References
Details
Attachments
(4 obsolete files)
This issue has been discussed during the latest all-hands.
I have a prototype that enables IDB, Cache, SW APIs to the private-browsing mode.
In order to avoid to expose the PB origins, they are replaced with null-principals. The private-browsing data usage is not exposed to getUsage().
I want to collect feedback. In particular I want to know if:
- the current approach is reasonable.
- how to improve the current code.
- what else must be done in order to land this feature.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D36496
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D36497
Assignee | ||
Comment 4•5 years ago
|
||
Depends on D36498
Comment 5•5 years ago
|
||
Andrea has already provided patches, so I guess he is the assignee. Please feel free to correct that if I misunderstood. :)
Assignee | ||
Comment 6•5 years ago
|
||
Can you please take a look at these patches?
Comment 8•5 years ago
|
||
We need to decide if we just want to wait for UUID based directories in QuotaManager, bug 1593365.
Comment 9•5 years ago
|
||
(In reply to Jan Varga [:janv] from comment #8)
We need to decide if we just want to wait for UUID based directories in QuotaManager, bug 1593365.
Do we have a decision here?
Comment 10•5 years ago
|
||
I'm really thankful for the ideas here, it helped us to design QM v4, but it would be better to just wait for QM v4.
Comment 11•5 years ago
|
||
Besides QM v4, our team will be also working on encryption support for IndexedDB, initiallly done for private browsing.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•2 years ago
|
Description
•