Open Bug 819496 Opened 12 years ago Updated 2 years ago

offline data domain is listed in non-private window

Categories

(Firefox :: Private Browsing, defect)

x86
macOS
defect

Tracking

()

People

(Reporter: jbecerra, Unassigned)

References

Details

(Whiteboard: [testday-20121207])

Using latest birch nightly, if I am in per-window private browsing mode and I visit a page that can request permission to store data for offline use, when the private browsing window is closed, the domain name (and possibly cached data) remains in the list of sites that can store data.

Steps:
1. Launch the browser and open a page.
2. Open a PB window using command-shift-p
3. Go to https://hacks.mozilla.org/2010/01/offline-web-applications/
4. Click on the todo demo link (shortened) http://is.gd/RNGOU6
5. When prompted, allow the site to store data for offline use.
6. Try addin a task
7. Close the PB window
8. Go to the advanced tab in preferences window and select the network section

Expected: There should be nothing about the site you just visited and allowed to store data

Actual: You can see developer.mozilla.org listed and some number regarding storage used.
Whiteboard: [testday-20121207]
Hmm, Josh I thought we fixed this at some point, but I can't find the bug number...
Unfortunately offline app storage uses the permission manager, which doesn't (and never has) had any concept of temporary permissions for private browsing. It's a problem, to be sure, but since this isn't a regression I don't think it needs to block the release of per-window private browsing.
This happens in the latest Fx18b3 as well.
(In reply to comment #2)
> Unfortunately offline app storage uses the permission manager, which doesn't
> (and never has) had any concept of temporary permissions for private browsing.
> It's a problem, to be sure, but since this isn't a regression I don't think it
> needs to block the release of per-window private browsing.

Agreed.  Who should be CCed here?
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.