diff options
| author | tonikitoo <tonikitoo@igalia.com> | 2016-08-08 16:14:05 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-08-08 16:14:05 -0700 |
| commit | 1c836753bb86b3eb0e130f1d92868a273bb26ab8 (patch) | |
| tree | 35a4cc074fc56bd53112492b48dece10e1519470 /testing/resources/pixel/bug_524043_3_expected_mac.pdf.0.png | |
| parent | 727da4f329956406b936ba9c0bc49ab2d32db67e (diff) | |
| download | pdfium-1c836753bb86b3eb0e130f1d92868a273bb26ab8.tar.xz | |
Add support to Document::gotoNamedDest method.
Patch implements the Document's API gotoNamedDest, which is
part of the PDF specification [1], page 129, with the following
(short) description:
"Use this method to go to a named destination within the
PDF document".
[1] http://partners.adobe.com/public/developer/en/acrobat/sdk/5186AcroJS.pdf
"Named destination" is a common concept in the PDF world.
It can be used together with PDF's Links, Annotations, Bookmarks
and OpenActions, as well as an action per se, in case "this.gotoNamedDest"
is called directly.
Note that the implementation makes use of the existing hook
CPDFDoc_Environment::FFI_DoGoToAction, which ends up calling
out the embedder to actually handle it.
In case of Chromium, for instance, it calls PDFiumEngine::Form_DoGoToAction
which only handles for now the "page" property of the "destination".
Other properties, including zoom level, and scroll position
are ignored for the moment.
BUG=pdfium:492
Review-Url: https://codereview.chromium.org/2221823003
Diffstat (limited to 'testing/resources/pixel/bug_524043_3_expected_mac.pdf.0.png')
0 files changed, 0 insertions, 0 deletions