![firefox os x 10.6.8 firefox os x 10.6.8](https://houstonretpa.weebly.com/uploads/1/2/5/5/125524819/139961260.jpg)
![firefox os x 10.6.8 firefox os x 10.6.8](https://img-18.ccm2.net/LvIrdLUBTD1OBi1VRPLUWZsxbQU=/500x/eeb235fc986f427bb810ee5b82b0b5e2/ccm-download/fox_dark.png)
However including the query string in the security domain for a file just seems problematical to me. One can certainly make an argument for default restrictive same-origin policies for files compared to how some other browsers do this. There should only have been one database file associated with the file URL's file name on disk. I would expect never to see such SQLite database files created with the query string in them at the end. It seems to me that the same local file should be in the same same-origin security domain regardless of the query string or how the file was opened. storage/persistent directory, a new database was made for the second test with the query string as: file++++Users+pdf+Documents+workspace+Pointrel20140331+source+PointrelBootstrapLoader.html+view=testįile++++Users+pdf+Documents+workspace+Pointrel20140331+source+PointrelBootstrapLoader.html
#Firefox os x 10.6.8 plus#
I can then flip between tabs which have the same URL (file and query string) and they show different content (or errors) based on how the URL (file plus query string) was loaded. I can save data with the bookmarked version, and it seems it is saved in a different database (listed below).
![firefox os x 10.6.8 firefox os x 10.6.8](https://linux-cdn.softpedia.com/screenshots/Mozilla-Firefox_3.jpg)
It seems Firefox is trying to load some other SQLite database file in this case. However, if I launch the single-page app via pasting in the file URL or via a bookmark, or by reloading the page by pressing the enter key at the end of the URL, then the data is not accessible if the URL has a query string. Firefox in this case seems to propagate the security domain to the new page that is opened from the previous page. The data remains even if I press the reload icon next to the URL area. Under Firefox 29 and also the Firefox Nightly I tried, what seems to happen is that if I launch a new page directly from the single-page app which has the same file but adds query string, the data is accessible via the same IndexedDB database. I did not test all the permutations of this before upgrading to Firefox 29, so perhaps I missed a nuance of this similar to later versions. The initially stored data was not accessible with different query strings at all, and the application reports creating a new database when accessed with a different query string. Under Firefox 28, it seems that any query string probably made the security domain for the same origin policy use a different SQLite database file. $samples/Full_IndexedDB_example?revision=543435 That is, the data previously entered was not accessible via the URL with the query string, and a second IndexedDB SQLite database is created under storage/persistent with the query string as part of the file name. I observed the same behavior as for the application I am working on described bedlow. Then I added a query string part ("?q=foo") to the URL and reloaded the page via pressing the "Enter" key. The new entry listed OK with "List database content". I then opened the file in Firefox, added an entry (title and Bibliographic ID, clicked "Add Publication"). I just tested that on Firefox 29 by saving the Mozilla IndexedDB tutorial demo to my local machine. Just open up such an application, run it, and then add a query string to the URL and press enter in the URL bar and your data will probably appear to go away. However, this issue should be duplicate-able with any simpler IndexedDB application that runs as a local file and for which you append a query string. This bug report is what happens when using that generated URL with a query string. Then click on the "Browse" button to open the saved content in another tab (or window) to view only that added content (with the app's editing features hidden). For this test, you would need to add a new item with some text such as "Hello world" (could be anything, including HTML with JavaScript), call it "test" as the Data ID, and "Store" it locally via that button. That single-page FOSS application is inspired by Mozilla Webmaker ideals, that anyone should be able to create and use web pages locally. The single-page application I am developing and testing with is at: However, when I start to add query strings to the URL after the file name, things start to behave unexpectedly. The application works fine when working without adding a query string.
#Firefox os x 10.6.8 mac os x#
Using Firefox Nightly (tested ) on Mac OS X 10.6.8, I opened a locally-stored HTML file which uses an IndexedDB database for a single-page application.