Steps to reproduce
While using adobe pdf reader extension in older versions of IE, one was able to jump to a specific pdf page by adding the page number at the end of the pdf url (like query string). I am unable to do that in the new edge pdf reader. Can you suggest how can I solve this particular issue?
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Brad E.”
Changed Assigned To to “Amit K.”
Changed Status to “Won’t fix”
Changed Assigned To to “Vyankatesh G.”
Changed Status from “Won’t fix”
Thanks for reporting this issue. We are aware of this limitation in the Edge browser and your query has been duly noted in our product backlog. But as we do not plan to take this up for the upcoming release cycle, I will have to close this issue for now. We will prioritize this change request based on more user feedback.
- Microsoft Edge Team
Changed Status to “By design”
Chrome can do it.
Yes, I’ve flagged this before, its an important feature, also issue with powerapps pdf reader for same reasons. Being able to have link for a user that directs them to a specific page on opening is very useful. All other browsers can do it.
Makes EDGE useless for opening PDFS, as everything is twice as hard to do when you do open one in EDGE.
Microsoft Edge 42.17074.1000.0 can do it!
It semi works - if you open the pdf from a url, then modify the url while viewing that page to include the page number it doesn’t work, going direct to a url with the page already appened does.
I’m a little confused. When trying to go back to the basic reader, it seems to insist that this new program is a much better fit, when it seems to provide a worse service than many other options. These is starting to feel like a recurring theme with a lot of these programs. It’s like how upon startup, when setting my default browser, it seems to be begging me to give this new guy a chance. I’m sorry, but I’d rather not have to deal with msn, as opposed to chrome. I don’t want to spend time trying to run these programs down. It’s only when I see this sort of endorsement interrupting my interactions to the point where I find it intrusive. I just wish the use of this practice (as small as it may seem now), would stop growing at the rate that it is.
This issue is also very important for me. Our customers can specify any browser they want as a default and Edge is the only one that doesn’t support named destinations. That this issue was twice marked “won’t fix” is just not acceptable, and this Microsoft Partner wants it taken care of!
Microsoft Edge still does not open local PDF files on named destination, few years after release and now more than 2 years after the report of the bug, while every other browser is able to do it, and status is “by design” which obviously means that this very useful feature will never be implemented.
I will have to recommend all the users of my program to stick to other browswers, for example, chrome.