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.
... View more