Bug with wide pages, resize to container, and strip mode

[tarrasqueSorcerer]

I use the reader in long strip mode and "resize to container" setting. I click pages to move to next page. I get to a wide page, and most of the time clicking starts misbehaving on next page and afterwards. Same applies to right arrow keyboard key and ">" button at the page counter.
Trying to go to next page does nothing unless I move the view at least slightly down. Trying to go back (left arrow key or "<" button) goes two pages back. Page counter in the corner shows previous page's number. In fact, looks like the root of this problem is incorrectly updated page counter

Example: https://mangadex.org/chapter/738796/1
Page 10 is wide. When I go to next page, page counter still says "10/29" even as page 11 is open. Basically the viewer still thinks I'm on page 10, so going forward moves me to page 11 (which I'm already on) and going back moves me to page 9 (which is two pages back). Moving slightly down updates the counter, but moving back up sets it back.
Another example: https://mangadex.org/chapter/57261/1
First page is wide, second page breaks.

However, somehow, https://mangadex.org/chapter/6109/1 doesn't break after wide page 4.

 

[babel]

Similar bug with long strip + fit to height. Adds weird width to page and breaks alignment & keyboard usage.

@Teasday -- hi again, apparently I have problems with my preferred long strip mode on a biannual basis now! All confidence you'll figure something out sharpish because you clearly know your stuff, and it's probably Chrome's fault again, though the interesting thing this time is that it's only after some pages load? Though some, like https://mangadex.org/title/41789/azur-lane-headpetting-shipgirls-doujinshi seem to have it straight away, making me think it wasn't displaying for a hot minute.

Demonstrated here https://youtu.be/XV5YeP4tu0s

 

[Teasday]

@tarrasqueSorcerer Can't replicate in Firefox or Chrome. I don't know what to tell you, this is the first time I'm even hearing of a bug like this.

@babel The reason that one happens is because the reader preloaded that chapter's final page, which is (at the original size) really wide and forces the page to essentially allocate enough horizontal space to contain it, even in fit to height mode. Frankly, I don't want to mess with it because the fit modes are a nightmare to get right, so you'd be better off just using fit to container.