Can we have a swicher for the default reader

[Quirriff]

The Classic reader works better most of the time....But sometimes it's better to use the default.

From the classic reader you can switch to the new one, but you can't switch to the old reader from the new one without going into settings and whatnot.

 

[MavB_Ver]

They don't recommend using the legacy reader, so making it hard to to switch to it is understandable.

 

[BraveDude8]

@Quirriff What scenarios are making you use the legacy reader? It's legacy for a reason, it's garbage and getting trashed with the site rework.

 

[Quirriff]

On some titles it simply works better and it's not as slow/doesn't bug out as much. but it's not a universal thing.


For example I sometimes get half-loaded images that are half-grey and switching image servers does nothing or constantly looping imaging loading.

 

[BzzBzz]

> works better and it's not as slow/doesn't bug out as much

Stop using Apple products with shit browser and get Android device with proper browser.
or
Stop using 10 y.o. browser and get a moderm one with proper support of modern techs.

 

[blackyawgdom]

"One cannot expect customer support in 2020 for using Windows 98"

 

[SushiBentou]

I use legacy most of the time too.

It's nicer to look at for me, the continuous image. More immersive imo.

It's better on slow connections. Load the whole chapter while doing something else.
It also prevents delayed load when clicking new page which I really hate, I switch to mangapark often when it happens.

edit> default reader also has excessive disk io. Every new page causes half a second of hdd activity.

 

[ixlone]

Half loaded images are a failure in data saving mode due to a corrupted file and not due to default reader.


It's worse on slow connections. It tries to load every page at once. If one page fails then you have to reload all pages again. Default reader allows single page reloading.

 

[Teasday]

_{@SushiBentou posted:}

edit> default reader also has excessive disk io. Every new page causes half a second of hdd activity.

I don't know what to tell you, the only thing even close to this that I can think of that we're doing is using the native browser caching API. Nothing the reader does should be creating any more disk activity than browsing imgur would.

The way you phrased this is ambiguous, though. By "every new page", do you mean an image downloaded or page turned? Because if it's the latter, I have absolutely no clue what would possibly be the issue there.

It's nicer to look at for me, the continuous image. More immersive imo.

This is also a feature on the newer reader though

 

[blackyawgdom]

Should save the trouble and pre-eliminate the legacy reader before v5. I mean iirc accounts made after a certain period dont have the option to switch, so why not expand to all. Netflix changed the UI all the time without asking people!

 

[Afiaki]

@BraveDude8 @Teasday
The new reader hides images until they're fully loaded.
On long-strip manga with slow connections this can minutes of waiting before anything becomes visible. I have been waiting for said minutes on said long-strip manga and came across this thread— page 1 still hasn't loaded yet has loaded only now that I have posted this comment.

I haven't got a reply from any developer yet, are you guys going to be removing this method of loading?
Every other manga site out there shows images as they load, this site is by far the "slowest" loading site I read on.