All Mangas Reader

The first thing is HEAD Request Loading-well basically I couldn't think of a adequate title but here is what I'm talking about:
When you go to the manga page (on I believe all sites) first the page_1 loads and then allmangasreader kicks in and reloads the first page and everything else. Now that is fine if your internet connection is good, but some people who have a bad internet connection this could be quite a problem or maybe we should say: annoyance. I believe it should be possible for allmangasreader to kick in BEFORE it loads the page but I don't have many ideas on how to do that for I haven't coded enough chrome extensions.

The second is Preload next chapter, all this does is consume bandwidth for me, the next chapter doesn't load any faster. I don't really know how its supposed to look because I haven't taken a look at the code but I'm assuming it loads the images in the cache. But when you go to the next chapter the page reloads so yes if the cache was working for me it would speed up the loading, but why not use javascript to simply remove all the image objects of the first chapter and show all the objects of the next chapter..?

Lastly another problem those with slow internet connection have. The chapter will load and then it'll say its complete but almost all of the chapters will still have the loading symbol on them not loaded, then one has to refresh the page. To fix this I would put that "try again" button on the pages that are loading (not after they've failed to load because that doesn't always occur).


Thanks for reading this I hope these changes can be made to make allmangasreader even better than it is

About the first idea, I must say that it can't be helped. Chrome waits until the page renderers to load our extension, and we need to work that way.

In all online readers, when the chapter changes the url changes and the browser start rendering the page, that is because it's easier to load several parameters, options, data, etc. that is specific of that chapter in that manga. That's about the second idea.

A try again button on timeout uh... in reality there is one but seems to only work when a error 404 is present. The problem with this is, that our scripts waits for response of the browser and it don't give a proper answer. This happens to me when I am using the pc + internet on heavy load. But still its an a welcoming option if the javascript can have a timeout if no bytes is received.

I think that all new features will be on hold until the new version get stable, and the site scripts updated.

_________________
Know about me

I didn't completely understand your second response. If one utilizes HTML5 one can adjust the url without reloading. I did it on a website I made, and it worked great, you can navigate the whole site and only ever reload the body. This is a chrome extension after all, why not utilize this HTML5 feature.

I believe simply adding an option so that if you ever click an image (loaded or not) it will reload. Those with good internet won't need the feature but those with bad will find it very helpful. Especially since I've noticed sometimes half of the image will be loaded for me and not the rest then I have to reload the whole page again.


But thanks for the replies.

In regards to your third problem, you're absolutely right, and i asked polo about it a while ago. I'll add it to the feature requests.

About your second one, I'm pretty sure it was tried but didn't work due to security functions built into chrome for their extensions. These security standards are only getting harder and harsher especially in respect to JavaScript, so I'll add it as well, but i don't know what good it will do.

About the first one, though i agree it would be incredibly cool, I'm not sure it's possible. But I'll add it in anyways xD

These are excellent ideas! Thanks for contributing.