-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Sending messages stopped working #7238
Comments
😲 Out of interest, do you have a rough idea of how long 'long enough' is in this case? |
A year, perhaps? Probably with some very long messages in my chat history. |
I cleared session storage and it's working again. |
oops, just answered this one by mail. you should just need to delete some disk space to stop the browser quotaing localstorage. |
(it’s a fundamental (mis)feature of localstorage and indexeddb that the browser can arbitrarily decide to stop storing data if it thinks you are running low on space) |
In any case, I'd suggest that this exception should be handled gracefully. Having the enter key just stop working is somewhat disconcerting. |
Related: #6120 |
I can't test this easily. Is the problem still there? |
it looks like a browser quota issue, nothing the app can do anything about |
Description
Impossible to send a message
Steps to reproduce
Use Riot for long enough. Type message, press enter, nothing happens.
Version information
For the web app:
The text was updated successfully, but these errors were encountered: