01ab15a6f1
Currently the `getPageIndex` method will happily return `0`, even if the `Ref` parameter doesn't actually point to a proper /Page dictionary. Having the API trust that the consumer is doing the right thing seems error-prone, hence this patch which adds a check for this case. Given that the `Catalog_getPageIndex` method isn't used in any hot part of the codebase, this extra check shouldn't be a problem. (Note: in the standard viewer, it is only ever used from `PDFLinkService_navigateTo` if a destination needs to be resolved during document loading, which isn't common enough to be an issue IMHO.) |
||
|---|---|---|
| .. | ||
| features | ||
| font | ||
| pdfs | ||
| resources | ||
| stats | ||
| ttx | ||
| unit | ||
| .gitignore | ||
| annotation_layer_test.css | ||
| downloadutils.js | ||
| driver.js | ||
| test_manifest.json | ||
| test_slave.html | ||
| test.js | ||
| testutils.js | ||
| text_layer_test.css | ||
| webbrowser.js | ||
| webserver.js | ||