Skip to main content
Participating Frequently
September 25, 2022
질문

Bug Report: Acrobat Chrome Extension does not respect page-specific PDF links

  • September 25, 2022
  • 3 답변들
  • 6232 조회

Acrobat’s Google Chrome extension is not respecting page-specific PDF links (My specs: Mac Book Pro 2021,  Monterey 12.6, Chrome 105.0.5195.125). This is really bad for my field, since we often have to link to specific pages of Federal Codes of Regulations, legal and public policy docs, etc. by page number. Normally, I can link to an online PDF by page number by adding the suffix "#page=X" after the .pdf at the end of the url. Without the extension activated, it works just fine. But the activating the extension results in the user being taken to the first page of the PDF, which defeats all our efforts in trying to be accountable and creating an online paper trail. I am begging you devs to fix this glitch, because we can't anticipate whether policy wonks will have the featured turned on or off. Thanks for listening.

3 답변

glennc62169268
Participant
April 8, 2025

This bug still exists in the Chrome ver 25.4.01 .  The acrobat extension will correctly process #page=1-9 but will not process double digit numbers.l

https://www.dnr.wa.gov/publications/ger_ri19_strat_yakima_basalt_ellensburg_form.pdf#page=9 goes to the correct page.

https://www.dnr.wa.gov/publications/ger_ri19_strat_yakima_basalt_ellensburg_form.pdf#page=10 goes to the first page.

 

this funtion works correctly in the Edge browser.l

Participant
October 10, 2025

After much searching I finally figured out the installed Adobe Reader extensions for the browsers will not naviage to any PDF URL that has #page= or #[destination anchor]. It simply ignores the page number or anchor in the URL string. Once I removed the extension from my browser, so it used the default simple PDF reader embedded in the browser, all my links worked. This works in Chrome (Version 141.0.7390.77 (Official Build) (64-bit) and Brave. It does NOT work in MS Edge as the Adobe Reader extension is embedded by default, so those URLs will not work in MS Edge. Thought I would share with everyone. Adobe needs to fix this issue in the Adobe Reader extension that users install in their browsers, as years later, it is still an issue in 2025.

Participant
January 27, 2024

Hi @Meenakshi Negi Do we have any update on this?

Meenakshi Negi
Legend
January 28, 2024

Hi Jeff in Boston,

 

Thank you for sharing the information. We will report it to the team and share this information for further investigation. We appreciate your patience. 

 

 

Thanks,

Meenakshi

Participant
May 15, 2024

There is still no update on this?   It has been going on for years and there are multiple different complaints.  How can this not be fixed by now?  One thing is for certain I will not be using Adobe Acrobat in my Chrome browser (will disable now) until this is fixed.  Is there any ETA on a fix?  This was originally posted in 2022?!

Meenakshi Negi
Legend
September 30, 2022

Hi Jeff in Boston,

 

Sorry about the delay in response.

 

Would you mind sharing more details about the issue?

Was it working fine before?

It would be helpful if you could share the video of the workflow when you open it on Acrobat’s Google Chrome extension and when you open it without the extension. It will help us to understand the issue better.

 

Thanks,

Meenakshi

Participating Frequently
October 5, 2022