Summary
When using IE to link to named destinations from local intranet web services, failure to position properly.
Same test using external webserver, IE works just fine.
Discussion
Adobe PDF files have a feature called Named Destinations.
These are like bookmarks, but can be put anywhere in a pdf page in a document.
They are useful because you can hyperlink directly to a PDF Named Destination in a PDF document, just like with HTML named anchor in an HTML document.
I set up an HTML page that used TARGET= to position the named destination in an IFRAME on the same page.
The problem was that while the positioning worked fine in Firefox and Chrome, with IE8, I would get variable results. Sometimes the named destination would come up fine...other times it would be a page and half off. Sometimes two pages off. Sometimes it would go to the completely wrong named destination...
This all happened when the html code and pdf were on a web server in our intranet. It also happened when all the files were on a local directory.
Then, I put HTML and pdf file on an externally accessible web server...and suddenly it worked just great! One thing I noticed is that the named destination page would come up immediately in the IFRAME, but the whole PDF document would continue to download in the background for a few seconds.
What causes problem?
I'm wondering if there isn't some rendering issue that doesn't show when there is some latency involved, but which is exposed when the file transfers faster because of being on an intranet (?) Any thoughts?
John Bailo
When using IE to link to named destinations from local intranet web services, failure to position properly.
Same test using external webserver, IE works just fine.
Discussion
Adobe PDF files have a feature called Named Destinations.
These are like bookmarks, but can be put anywhere in a pdf page in a document.
They are useful because you can hyperlink directly to a PDF Named Destination in a PDF document, just like with HTML named anchor in an HTML document.
I set up an HTML page that used TARGET= to position the named destination in an IFRAME on the same page.
The problem was that while the positioning worked fine in Firefox and Chrome, with IE8, I would get variable results. Sometimes the named destination would come up fine...other times it would be a page and half off. Sometimes two pages off. Sometimes it would go to the completely wrong named destination...
This all happened when the html code and pdf were on a web server in our intranet. It also happened when all the files were on a local directory.
Then, I put HTML and pdf file on an externally accessible web server...and suddenly it worked just great! One thing I noticed is that the named destination page would come up immediately in the IFRAME, but the whole PDF document would continue to download in the background for a few seconds.
What causes problem?
I'm wondering if there isn't some rendering issue that doesn't show when there is some latency involved, but which is exposed when the file transfers faster because of being on an intranet (?) Any thoughts?
John Bailo