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

iOS - quota exceeded callback not fired #5

Open
jhruby opened this issue Jun 12, 2013 · 5 comments
Open

iOS - quota exceeded callback not fired #5

jhruby opened this issue Jun 12, 2013 · 5 comments

Comments

@jhruby
Copy link

jhruby commented Jun 12, 2013

If user does not allow to increase quota, there is no error callback called on setItem.

@WebReflection
Copy link
Owner

which device/browser are we talking about? is it all of them or WebSQL only? (or IndexedDB only)

@jhruby
Copy link
Author

jhruby commented Jun 13, 2013

WebSQL on Safari (on iPhone/iPad/Mac OS X)

@WebReflection
Copy link
Owner

iOS version ? (so I can test properly ... but yeah, something looks broken there in such case)

@jhruby
Copy link
Author

jhruby commented Jun 13, 2013

iOS 5

@WebReflection
Copy link
Owner

OK, the errorback is always invoked, unless you do some operation without passing it.

Can I ask you to show me an example that fails ? Or can you at least tell me how you update/save/set the record that fails? this is because if you specify a callback at the beginning for the error, this won't be used later on but only during initialization. If this is the case, pass the same callback until I change code so that by default, every other call will use the initial callback for the error, thanks.

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

2 participants