I am attempting to run my web app on an android tablet.
Everything works as expected except when trying to view an HTTP .pdf link.
We are using the native browser and it does not present a download link or display a second tab showing the page.
If I use the Chrome browser then I get the download icon which opens the document as expected.
The reason I am told we are using the native browser is so we can only present the application icon to the user on the desktop that will link directly to the app.
That is all the end user sees.
A well-formed web response would return a Content-Type HTTP header. Specifically, I think Content-Type: application/x-pdf
How a given content type is handled is up to the client being used, which often has a MIME-mapping table in it to help direct the content to the desired targer (whether it's a browse window, file download or something like a PDF viewer).
You used the term "native browser", so I'm going to interpret that as being the default webapp browser provided by the device vendor. Not knowing who the device vendor is, that's as far as I can go.
If you have written an app that itself contains a (webkit) browser control, then it's going to be your app that has to deal with the Content-Type handling.
Science is the process of replacing what we "know" with what is TRUE. Politics, alas, often prefers to be the opposite.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop