You would need to look at a variety of browsers. I only quoted Firefox claim. One maybe-not-critical point is that browsers might use the internal display of file extensions that they know how to display, such as .pdf
.
For cases of browser-internal viewers, there may be a question of how the tabs or windows operate, which sometimes is under user control, for those who know their browser well. For example, does the file preview open in a new tab to the right, replace the Duplicati GUI page (if so, make sure one can get back), pop up a new window (beware of popup blockers, and does this sort of thing require JavaScript), or something else?
I suppose there is also a chance that links (especially for unknown extensions) could use a viewer that’s a different web browser on that system (e.g. if association was set), which would maybe look a little strange.
Although I haven’t tested with an HTML link, testing from the address bar with a file://
link to a local file, then looking around with Process Explorer found both Firefox and Chrome seemingly invoking the external program through Explorer (it’s the parent process of the viewer, and one can see the exact invocation line).
Both programs started the viewer with the original file path, but Chrome downloaded the file first (clutter…) reminding me that a cleanup scheme of some sort would be preferable, if a preview scheme is automated.
Your web development skills seem pretty good, so if you would like to look at code, the HTML part of this is:
https://github.com/duplicati/duplicati/blob/master/Duplicati/Server/webroot/ngax/templates/restore.html
It would be nice if this only needed HTML and JavaScript (maybe AngularJS) work, because it eases finding the right set of developer volunteers to do it. If you want to look into whatever you can do, that would be nice.
Pull requests can be submitted, and community help for any part of Duplicati helps keep the project moving.