That's what I thought!
So, what's the point of these PDF extensions . . . extra functionality?
Note: After disabling both PDF extensions I have, PDF files now open correctly in Chrome. However, previously (before I checked the "allow access to file URLs" in the only enabled extension), the original problem was evident even when no extensions were enabled.
Nothing really. Some are useful, but now days too many of them are not needed with all of the changes that have been done with modern day browsers. Some of those extensions for Chrome are left over from when Google was still working on the PDF portion in Beta. The only extension that I use that interacts with the OS is the Mailto:, so that when I click on a email address, it goes to Yahoo Webmail, since Chrome does not have the ability to set it to take those links and open Mac Mail.
Hmmm . . . I spoke too soon. The original behavior has returned.
Clicking a PDF file in the mapped network drive returns an index of that file's parent folder (as described in my very first post).
The latter . . . mapped network share accessed via Explorer.
Again, I've had no problem opening PDF files stored on the NAS in the past. And there's been no setup or update change with the NAS that could explain this new behavior.
I suspect it's more likely associated with a Win10 update.
Quote