Here's one thing that's a bit unfortunate.
The period when this issue was present was from around May 31 (or possibly before that) till today, June 3, when the feeds were fixed. But if a user happened to have used the overtooning method during this period, it'll set something "bad" in their Local Storage, and so, even now that the feeds are fixed, the overtooning method still won't work for this user.
Example of a "bad" value in Local Storage:
For the domain http://comico.toast.com of course.
Key:
overloaderData
Value:
{"feedList":[{"url":"http://bumblebits.net/oddsquad/feed","name":"Oddsquad","lastUpdate":23885657,"teamUrl":"http://www.oddsquad.org"},{"url":"http://blackhorus.bumblebits.net","name":"BlackHorus Scans","lastUpdate":0}],"webtoonList":[]}
The way to fix this... well, the simplest way for a "normal" person is to clear cookies. That'll clear cookies and Local Storage. But of course, that signs you out of all sites you're signed into, which could be a bit annoying.
The "better" but more technical fix is to delete that specific faulty entry in Local Storage in the Developer Tools. But that might be a scary voodoo ritual to ask a "normal" person to do.
Another solution would be to go to any page on Comico (such as the FF chapter page), then in the address bar, type:
javascript: (you cannot paste this at least in Chrome and Firefox, so you have to type it)
Then right after that text, paste this:
localStorage.removeItem('overloaderData');
So it should look like this in the end:
javascript:localStorage.removeItem('overloaderData');
Then press Enter.
This would remove the faulty entry that prevents the overtooning method from working correctly.
BTW, just curious, what exactly is Local Storage used for in this case? I haven't looked at the whole code in great detail, so I'm not sure what exactly it's for, but I think it's to cache the feeds or something? Is it really necessary to be using Local Storage though?
Thanks!
last edited at Jun 3, 2015 10:15PM
