You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [X] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request
In chrome (haven't tested in other browsers), when you click click the up or down arrows in the input cell a few times quickly an infinite loop is created. It looks like the input value is not updated until after the page is rendered so there is some delay and then it gets re-updated.
For instance, if you start on page 1 and click up fast... 2, 3, 4, 5, 6, 7, 8, 9, 10, then it will start going 8, 10, 8, 10, 8, 10 over and over without any user input.
You can observe this behavior at https://vadimdez.github.io/ng2-pdf-viewer/ by uploading a multi-page document (mine is 82 pages) and then clicking the next button quickly, until you reach page 10 or so.
Due to this fix, pageChange doesn't fire at all, unless one enters an invalid page number.
const orginalPage = _page;
if (this._pdf) {
_page = this.getValidPageNumber(_page); // if _page is valid, it'll stay the same as orginalPage
}
if (orginalPage !== _page) {
this.pageChange.emit(_page);
}
Bug Report or Feature Request (mark with an
x
)In chrome (haven't tested in other browsers), when you click click the up or down arrows in the input cell a few times quickly an infinite loop is created. It looks like the input value is not updated until after the page is rendered so there is some delay and then it gets re-updated.
For instance, if you start on page 1 and click up fast... 2, 3, 4, 5, 6, 7, 8, 9, 10, then it will start going 8, 10, 8, 10, 8, 10 over and over without any user input.
You can observe this behavior at https://vadimdez.github.io/ng2-pdf-viewer/ by uploading a multi-page document (mine is 82 pages) and then clicking the
next
button quickly, until you reach page 10 or so.The text was updated successfully, but these errors were encountered: