I thought we were talking much more calmly.
Sorry, I didn't mean to give an aggressive impression or anything, I was and am just talking normally. I know some people read into me talking harsher than I think I am, but it's difficult to unlearn.
You said you wanted to know chrome too but now it becomes the same. If you wanted specifically firefox you should have just said so.
Well, to be fair it was Brave who said that, not me. And while I'm throwing him under the bus, he probably should've said "and" instead of just using the slash.
Anyway, it being possibly narrowed down to a Chromium thing makes more sense. What doesn't make sense is, like I said, is that it only affects some chapters and not others - whether the effect is on the majority of pages or not doesn't matter, it's the inconsistency that's weird. It being an issue for you on another phone as well would seem to narrow it down too, but unfortunately you're still the only one reporting this issue and I just can't replicate it on my OnePlus on any of the three browsers, even when checking the chapters you linked.
In short, I just can't think of what even
could be the problem. The page click code can't get simpler. Loading or node issues shouldn't cause that kind of a problem. The only thing that comes to mind is that you're somehow hitting an invisible element that's eating the click (which I can't find either), but that wouldn't be solved by double tapping instead anyway.