Fix for PDFs with lots of named destinations take a long time to load.

chrome/test/data/pdf/navigator_test.js

Index: chrome/test/data/pdf/navigator_test.js
diff --git a/chrome/test/data/pdf/navigator_test.js b/chrome/test/data/pdf/navigator_test.js
index d068a96ec81dc350ff6995ff313a7fdb8dc36b4b..8e4fcfa4591b19c9fc29d227a3479408aae85eaa 100644
--- a/chrome/test/data/pdf/navigator_test.js
+++ b/chrome/test/data/pdf/navigator_test.js
@@ -76,18 +76,6 @@ var tests = [
     chrome.test.assertEq(0, viewport.position.x);
     chrome.test.assertEq(300, viewport.position.y);
 
-    mockCallback.reset();
-    navigateInCurrentTabCallback.reset();
-    // #ABC is not a named destination in the page so viewport should not
-    // update and viewport position should remain same. As this link will open
-    // in the same tab.
-    navigator.navigate(url + "#ABC", false);
-    chrome.test.assertFalse(mockCallback.wasCalled);
-    chrome.test.assertTrue(
-        navigateInCurrentTabCallback.navigateInCurrentTabCalled);
-    chrome.test.assertEq(0, viewport.position.x);
-    chrome.test.assertEq(300, viewport.position.y);

[raymes, 2015/02/16 02:02:31]

How come this is removed?

[Deepak, 2015/02/16 06:45:38]

This is removed as:
when #ABC is not in paramsParser.namedDestinations.
so then it will fetch that #ABC from the plugin, via
getNamedDestinationFunction_() that function is provided by pdfviewer while
making OpenPDFParamsParser object.

Even if we provide this function while creating OpenPDFParamsParser() then this
callback will get called, and navigator callback will not receive call as that
will happen after receiving message from plugin.
So this case is not relevant here.

[raymes, 2015/02/16 22:44:03]

If we do the suggestion above we should be able to keep this test.

-
     chrome.test.succeed();
   }
 ];