You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to start by saying thanks for the excellent work you've done. It's been a valuable tool for me.
I'd like to suggest a change regarding how the count number is stored. Currently, you're using localStorage, which caused an issue for me. I tried setting the count to 1024000, which led to a crash as expected. However, what's more concerning is that even after reloading the web page, it continued to crash repeatedly. Due to JavaScript's single-threaded nature, it is difficult to change the count to a smaller number.
Could you consider storing the count in an alternative approach such as URL search parameters? This change might help prevent such crashes.
The text was updated successfully, but these errors were encountered:
Yeah, using a URL search parameter is a good idea!
At first LocalStorage was useful in switching and comparing the same amounts. But with huge counts like 100k it's better to get rid of that.
I want to start by saying thanks for the excellent work you've done. It's been a valuable tool for me.
I'd like to suggest a change regarding how the count number is stored. Currently, you're using localStorage, which caused an issue for me. I tried setting the count to 1024000, which led to a crash as expected. However, what's more concerning is that even after reloading the web page, it continued to crash repeatedly. Due to JavaScript's single-threaded nature, it is difficult to change the count to a smaller number.
Could you consider storing the count in an alternative approach such as URL search parameters? This change might help prevent such crashes.
The text was updated successfully, but these errors were encountered: