Skip to main content
J
Jeff in Boston
Participating Frequently
September 25, 2022
Question

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

  • September 25, 2022
  • 3 replies
  • 6180 views

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 replies

    glennc62169268
    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

    C
    Cachet Design Studio
    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.

    L
    lone_wanderer96
    Participant
    January 27, 2024

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

      Meenakshi Negi
      Community Manager
      Meenakshi NegiCommunity Manager
      Community Manager
      January 28, 2024

      Hi Pruthvi35073619dak4,

       

      Thank you for reaching out.

       

      We currently have no update. However, we will check with the team again. Could you share a sample PDF so we can replicate the behavior on our end? Please also share the version details. 


      Thanks,

      Meenakshi

        J
        Jeff in BostonAuthor
        Participating Frequently
        January 28, 2024

        Hi I originated this bug report, and created the demo video showing your developers how to replicate the error in clear and precise language. Your team has no reason to dither and delay on solving a situation that effects anyone and everyone who views an Adobe PDF with the in-browser Acrobat app activated. 

         

        I have attached the (508-compliant) PDF that I use in the demo video upthread, though I refer you to the official landing page for the resource portal of the U.S. Department of Housing and Urban Development at this publically facing link (https://www.hudexchange.info/resource/6679/ehv-roadmap-waivers-and-alternative-requirements/), so you understand the scope of audience and urgency of the matter.

         

        It has been a year since I brought up this issue and nothing has been done. You have a great product in Acrobat Pro with all the tools necessary to remediate a document to 508-compliance, but integration with the in-browser app leaves a lot to be desired from an accessibility point of view and this is inexcusable behavior from an industry leader in accessibility products. Thank you for listening.

          Meenakshi Negi
          Community Manager
          Meenakshi NegiCommunity Manager
          Community Manager
          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

            J
            Jeff in BostonAuthor
            Participating Frequently
            October 5, 2022

              Terms & ConditionsAccessibility statement
              Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices