Ensure that the PDFHistory._maxUid
property is correctly updated when initializing/navigating the history
This is a follow-up to commit e7721243399773fbc549ecb9ce83822df08dacde, in PR 8994, to cover a couple of cases missed there.
This commit is contained in:
parent
5a52ee0a79
commit
448a7a27cb
@ -133,6 +133,9 @@ class PDFHistory {
|
||||
let destination = state.destination;
|
||||
this._updateInternalState(destination, state.uid,
|
||||
/* removeTemporary = */ true);
|
||||
if (this._uid > this._maxUid) {
|
||||
this._maxUid = this._uid;
|
||||
}
|
||||
|
||||
if (destination.rotation !== undefined) {
|
||||
this.initialRotation = destination.rotation;
|
||||
@ -510,6 +513,9 @@ class PDFHistory {
|
||||
let destination = state.destination;
|
||||
this._updateInternalState(destination, state.uid,
|
||||
/* removeTemporary = */ true);
|
||||
if (this._uid > this._maxUid) {
|
||||
this._maxUid = this._uid;
|
||||
}
|
||||
|
||||
if (isValidRotation(destination.rotation)) {
|
||||
this.linkService.rotation = destination.rotation;
|
||||
|
Loading…
x
Reference in New Issue
Block a user