From 448a7a27cbbab63d72d2eecedb681d29b09e50b4 Mon Sep 17 00:00:00 2001
From: Jonas Jenwald <jonas.jenwald@gmail.com>
Date: Thu, 11 Jan 2018 12:06:44 +0100
Subject: [PATCH] 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.
---
 web/pdf_history.js | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/web/pdf_history.js b/web/pdf_history.js
index 756a4de54..57a4d1bbd 100644
--- a/web/pdf_history.js
+++ b/web/pdf_history.js
@@ -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;