Pinch zoom with infinite-scroll mode would not stay in the same page

[en-nicolabaesso]

Hi! I'm having an issue, as provided in the title, with the pinch zoom gesture (on both Android and iOS devices) while setting the viewer in infinite-scroll mode.
Here's what I observe: when in 'multiple' page mode, I can zoom without issues on a single page. When I switch to the 'infinite-scroll' page mode, no matter what page I'm on, doing a pinch zoom would result in a scroll to the first page.
Below there's a video demonstrating the issue. I believe I'm missing something altogether, or I'm using the 'infinite-scroll' mode the wrong way. Is there a method to have the zoom focusing on a single page? I'm already detecting if I'm in a specific page by doing this (because, as I understand, in this mode the PDF is rendered as a single, very long page):

const pages=document.getElementsByClassName('page');
this.currentPage.set(Array.prototype.slice.call(pages).filter((el:HTMLDivElement)=>{
    const rectEl=el.getBoundingClientRect();
    let isScrolled: boolean;
    isScrolled=rectEl.top <= (window.innerHeight || document.documentElement.clientHeight)/2
    return isScrolled
}).length);

Below is a video example of the issue.
This issue also occurs while programmatically setting the zoom level.

screen-20251107-145303.mp4

Let me know if you need more informations about it. Thank you!

Describe the bug
I reproduced the issue this way:

1. Load a multi-page PDF document (the issue is not related to a specific document)
2. Set the viewer in 'infinite-scroll' page mode
3. Scroll to a page > 1 (so not the first one)
4. Do a pinch zoom gesture

Version info

• Tested version is 23.3.1, on Angular 19

[stephanrauh]

Sorry for replying late. I was ill, and if I'm honest, I still haven't fully recovered.

I've manage to reproduce your bug. Most of the time, this means I've almost solved the issue - but I'm afraid, it's more difficult in your case. Pinch-zoom tends to cause issues that aren't solved easily.

I'm scheduling it for version 25, which means it's high priority. But before, I'd like to publish version 25.6.0. If you don't hear from me, say, one week after publishing version 25.6.0, please nudge me.

[en-nicolabaesso]

Thank you for the feedback. Glad the issue could be marked outside my application, I was genuinely worried about messing up with the settings..
Ok, I'll write a comment here if I don't hear back for you. Just out of curiosity, what is the main reason for this behaviour?

Last but not least, have a good recovery! A bug can wait, personal health can't.