Open Bug 1562669 Opened 1 year ago Updated 7 months ago

Expose quota-manager APIs in PrivateBrowsing

Categories

(Core :: Storage: Quota Manager, enhancement, P2)

enhancement

Tracking

()

ASSIGNED

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:

  1. the current approach is reasonable.
  2. how to improve the current code.
  3. what else must be done in order to land this feature.

Andrea has already provided patches, so I guess he is the assignee. Please feel free to correct that if I misunderstood. :)

Assignee: nobody → amarchesini
Status: NEW → ASSIGNED
Priority: -- → P2
Blocks: 781982

Can you please take a look at these patches?

Flags: needinfo?(jvarga)

Yes, I'm looking.

Flags: needinfo?(jvarga)

We need to decide if we just want to wait for UUID based directories in QuotaManager, bug 1593365.

(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?

Flags: needinfo?(jvarga)

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.

Flags: needinfo?(jvarga)

Besides QM v4, our team will be also working on encryption support for IndexedDB, initiallly done for private browsing.

Attachment #9075171 - Attachment is obsolete: true
Attachment #9075170 - Attachment is obsolete: true
Attachment #9075169 - Attachment is obsolete: true
Attachment #9075167 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.