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

[Jeff in Boston]

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.

[MeenakshiNegi]

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

[Jeff in Boston]

Hi @MeenakshiNegi,

Thanks for responding. I posted a Zoom video illustrating my workflow for replicating the bug in MAC OS Chrome as you suggested. I also asked a relative to reproduce my workflow on a PC to see if it affected Chrome users in Windows, and they said they encountered the exact same problem.

In retrospect, I did not have the proper terminology when I referred to #page=PageNumber as a suffix (Sorry, I'm a graphic designer, not a developer). After reading Wikipedia's article on URI syntax, however, it would seem that Acrobat Chrome Extension preserves the mail URL (behind some encrpyed garble), but is stripping away the fragment component or is failing to pass the fragment component #page=PageNumber as a parameter. I guess the question is does Adobe Chrome Extension hope to support page fragment identifiers in the future? If Adobe cares about accessibility and backward compatibility, I feel that this suppport needs to be built into the extension because if not, it will undo decades of work at the federal and state level in producing page-specific online paper trails intended to demonstrate accountability.