Longstrip Image Loading :fixed:

[Keryx]

Hi theire ,
first of I‘m pretty new to MangaDex and I love it .
But my gilfriend and I both experierenced an slightly annoying problem.

We both read the mangas using the longstrip Format. When we open a chapter (I think it‘s mostly in longer Chapters) not all Images get loaded while scrolling down.
I guess maybe the ajax call doesen‘t get triggert when you scroll down after the the inital loading is already done. The button for turning to the next chapter also won‘t be displayed.
Here is an example chapter where I experienced the problem I mentioned: https://mangadex.org/chapter/520681/5

The only chance to see all images is than to refresh the page and scroll to the end as fast as possible while the page is still loading. Then you can scroll to the top again and start reading.
I also changed the preloaded images to the max value of 20 without success.

While refreshing I also exprierenced somites that the previous chapter is displayed instead of the current one. I don‘t know how to reproduce this.

We both use the newest mobile chrome for IOS on an ipad.

English is not my native language so feel free to ask if my expressions are to weird ^^.
Thanks for hosting this great page

 

[Holo]

@Teasday

iPad issue?

 

[Keryx]

I don‘t think that the Problem is the Ipad OS itself.
It could be a problem of the browser ofc.
I could replicate the problem with firefox and safari as well.

I also found a way off getting a javascript console output. Because I sadly don‘t have access too any developer tools with the mobile versions of the browser. By opening chrome://inspect/ in a seperate tab I logged the javascript output.

I got following javascript error thrown each time the loading error occured

I researched a little bit and it seems to be a built in spam protection exception which is thrown by the browser and results in an javascript crash.

I could‘nt reproduce the error on the android versions of firefox and chrome by using my smartphone. So it seams to be a kind of apple problem –_–.
Well i don‘t know if you can catch that exception in your javascript or maybe or prevent the error itself. But I also can understand if that is to much of effort for only one kind of device.

Thanks for taking your time and answering that fast

 

[Teasday]

@Keryx Oh, that's an interesting error, thanks a lot for digging it out. I didn't imagine it could become a problem. I'll do something about it.

 

[Keryx]

@Teasday

thank you so much . If you don‘t have a device to reproduce the error I can test it again after you found a solution.

 

[Teasday]

@Keryx Hey, sorry this took a while. I added a thing that makes the history.replaceState happen at most once every 100ms. That's still so low that 100 times per 30 seconds might happen if you're quickly scrolling up and down for 10 seconds straight, but I also wrapped it in a block that should catch the error and at most print a warning.

Whether that actually solves the specific issue you had in the original post, I'm not completely sure.

 

[Keryx]

@Teasday
No problem take the time you need .

I think the problem occours now less often. But sometimes it still happens. I think that’s only the case if you scroll super fast to the bottom while loading. So this won‘t hopefully not be a problem while reading

Also there is an error at the place where you catch the error

I believe the function is called with console.warn().

Sorry for all this trouble.

 

[Teasday]

oh my lord this has to be the dumbest mistake I've made

alright, warning changed to warn

 

[Keryx]

Naaa could happen to anyone ^^

Now the warnings are logged and the page keeps loading.
I tried it several times.

But 2 times while loading a chapter I got a new kind of error (I’m so sorry ._.)
I don‘t know how I can reproduce this.
I think it probably doesen‘t have to do anything with the loading problem?!
So maybe this is an helpful information for you ^^ or not

I guess the issue is solved . Thanks so much for taking your time!

 

[Teasday]

The wrapper thing is related to my pretty recent rewrite of how rendering works, and longstrip in particular is quite a pain in the ass to get correctly. As long as it's relatively rare, I think I'll just shrug and try to improve it with the next reader iteration.

Thanks for letting me know about this issue in general, I learned something new to hate about iOS lol.