Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script-scoped localStorage and IndexedDB? #1768

Closed
kulmegil opened this issue Jul 17, 2013 · 6 comments
Closed

Script-scoped localStorage and IndexedDB? #1768

kulmegil opened this issue Jul 17, 2013 · 6 comments
Milestone

Comments

@kulmegil
Copy link

It would be nice to have those two mechanism at script disposal - that is data shared across domains and being isolated from page content.

as a side note:
I had tried accessing localStorage from iframe loaded with GM_getResourceURL() - hoping that since gm special protocol produces same URI for a resource on each site it would work but at the end I was still accessing site ls :(

@arantius
Copy link
Collaborator

arantius commented Aug 8, 2013

I think this would be nice. Last time I tried something like this, I failed. Lots of behavior baked deep into the browser that wanted to tie these tools to the content scope, and thus breaking them in script scope.

Not saying it's impossible, but it's difficult enough to be quite low on the priority list.

@jerone
Copy link
Contributor

jerone commented Jan 22, 2014

We have SQLite now; #1798

@arantius
Copy link
Collaborator

Yes, that per-script DB exists, but only the legacy get/set APIs are supported. It would be nice to expose a richer (SQL?) syntax directly to scripts. But like I said, earlier attempts at doing so were not successful.

@arantius
Copy link
Collaborator

Ah and this is largely a dupe of #1212 .

@bombledmonk
Copy link

It would certainly be of great help in several of my scripts to have even rudimentary SQL access for multiple table columns. (in the scale of 100MB of data currently in csv)

@arantius
Copy link
Collaborator

arantius commented Mar 6, 2014

This is definitely a feature I'd like to have. If you have time to implement it, I'd happily review pull requests. It might be easier since #1798 took care of creating a separate storage DB per script, i.e. just create new table(s) there? I still don't know if it's possible/practical to safely export access to it into script space.

@arantius arantius modified the milestones: Pony, Bankruptcy Jul 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants