Was only noticeable in the mobile reader ui because the desktop one hides this component and uses its own logic. It resulted in the previous/next button not being clickable because the current page component was overlaying it
Was only noticeable in the mobile reader ui because the desktop one hides this component and uses its own logic. It resulted in the previous/next button not being clickable because the current page component was overlaying it