Download versus View PDF confusion

[StephDriver]

Issue identified in #4194 Screen reader testing.

• Sample 4, item 8. download / view PDF have same functionality in some browsers, unless you override?

Having these two links adjacent to each other is confusing when they have the same functionality in some browsers. Either we should force the download functionality to override and download, or have only one of them.

[mauromsl]

We already set the correct headers to indicate to browsers that the file is to be downloaded:

< HTTP/1.1 200 OK
< Server: nginx/1.18.0 (Ubuntu)
< Date: Mon, 03 Jun 2024 09:19:29 GMT
< Content-Type: application/pdf
< Content-Length: 4402301
< Connection: keep-alive
< Content-Disposition: attachment; filename="olh-10191-sutton.pdf"

Some browsers, even though they will correctly download the PDF, the do indeed immediately open the PDF, however it is done from a local URI, rather than from our URL. Some of our partner presses still want these metrics to be collected separately. If we were to only have one link, we would no longer be able to provide a download/view report accurately, and thus would need to provide a compelling reason to them.

[StephDriver]

I've just tested this again on desktop, and observed the behaviour described by @mauromsl so I think the original behaviour I observed may have been because I was testing on a smartphone

In which case the only concern I have that remains is having both 'download' and 'view' under the heading 'download'.