-
Notifications
You must be signed in to change notification settings - Fork 16
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
geeksquiz.com matching #2
Comments
According to the same origin policy .. we can't access localStorage or cookies of any other domain. |
Cloud will indeed take too much effort.
Imo the client-side storage solution is perfect - the users store the data for themselves - it's just the different domains that are hampering us. Can we not access The problem with using an invisible iframe to make Also, I found PouchDB but I'm not sure if it would work. I think we ought to request the moderators of geeksforgeeks to add the iframe bit to their servers. We ought to reason with them that the extension will benefit users a lot. Other than this, we could look at solutions which don't involve a front-end (like the widget you've made). I'm out of ideas. |
Hey, your latest master branch code doesn't include the changes from PR #1.
It would be nice if you could re-introduce those changes please.
Edit: After a bit of debugging, I see why you had to remove the feature.
localStorage
is different for different domains. Surely there must be a way to overcome this problem. It seems that most solutions which try to grow the concept oflocalStorage
into cross-domain functionality depend on server-side changes.Can't we store the data elsewhere?
The text was updated successfully, but these errors were encountered: