I would like to report an observable behavioral difference regarding page‑open actions (/AA /O) when opening page 2 of a sample PDF document.
- Pages 2–9: each page has a page‑open GoTo action pointing to the next page.
- Page 10: contains a text field and a page‑open ResetForm action.
- Page 2 is used as the entry point for testing.
- 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9 → 10 → ResetForm
The results are as follows.
1. Viewers in which the full action chain executes automatically
- Adobe Acrobat Reader Continuous Release Version 2026.001.21691
- Foxit PDF Reader / Foxit PDF Editor Version 2026.1.2.36540 (64 bit)
- Nitro PDF Pro Version 26.0.10.0
- PDF Studio Pro 2024 Version 2024.0.1
- Google Chrome PDF Viewer Version 150.0.7871.182 (64 bit)
- Microsoft Edge PDF Viewer Version 150.0.4078.83 (64 bit)
- In these viewers, opening page 2 results in automatic navigation through pages 3–10, and the ResetForm action on page 10 is executed.
- PDF‑XChange Editor Version 11.0.1
- Opening page 2 triggers the GoTo action to page 3.
- When page 3 is displayed, its page‑open action does not execute.
- The chain stops at page 3.
- Page 10 is not reached, and the ResetForm action is not executed.
- Firefox PDF (PDF.js) Version 153.0
- Sumatra PDF Version 3.6.1 (64-bit)
- PDF Annotator Version 10.0.0.1011 (64 bit)
- These viewers do not execute page‑open actions in this document and are therefore not included in the comparison of cascading behavior.
A short comparison video is attached showing:
- The behavior in PDF‑XChange Editor (chain stops at page 3).
- The behavior in Acrobat Reader (full chain executes).
rakunavi
- PDF-XChange Editor PRO Version: 11.0.1
- OS Version: Windows 11 Pro / Home 25H2 Build 26200.8875
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL