If I create a brand new destination within a PDF using Acrobat Pro DC, then host that PDF on a web server, and then open up and navigate to that Destination via a web browser via the #[Destination] or #nameddest=[Destination] anchor tag (it makes no difference which browser), it will properly take me to that destination. However, if I then change that Destination in Acrobat Pro DC by moving to a different location in the document, and using the "Set Destination" option in the context menu of the Destination, and then rehost the PDF on a web server and attempt to navigate to the Destination again, it will not properly navigate to the new Destination location. I have to delete the Destination and recreate it for the Destination to be properly navigated to within the browser.

Interestingly, within Acrobat Pro DC, it will navigate to the new Destination location if I double-click the Destination. But the browser will not. The browser will open up the first page in the PDF. It does not seem to recognize when a Destination's location has changed. The Destination has to be deleted and recreated.

It seems as if the behavior behind the "Set Destination" option in the Destination's context menu does not reflect all of the same behavior behind creating a brand new destination; like perhaps there's a property that should be getting set that isn't, which might be specific to browser plug-in behavior but not the native behavior within Adobe Pro DC.