Open
Bug 1144017
Opened 9 years ago
Updated 2 years ago
IndexedDB storage for the same file:// URL in different places depending on history
Categories
(Core :: Storage: IndexedDB, defect, P3)
Core
Storage: IndexedDB
Tracking
()
NEW
People
(Reporter: darktrojan, Unassigned)
Details
Assuming I have an HTML file that uses indexedDB at /home/geoff/foo/bar.html: If I go directly to that page, the storage is at [profiledir]/storage/default/file++++home+geoff+foo+bar.html However, if I first visit file:///home/geoff/foo/ and then click on bar.html, the storage is at [profiledir]/storage/default/file++++home+geoff+foo+
Comment 2•9 years ago
|
||
Yeah, I've noticed this strange behavior, but haven't investigated it yet.
Flags: needinfo?(Jan.Varga)
Updated•6 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•