[GH-ISSUE #126] Feature request: open PDF files in browser #125

New issue

Closed

opened 2026-02-27 15:55:09 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:55:09 +03:00

Owner

Originally created by @gdelugre on GitHub (Jan 31, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/126

After searching for a PDF document, the next thing I generally want to do is to open it and read it, without necessarily saving it to on my local machine.

However the server returns a Content-disposition header that makes the file to be downloaded instead of being opened in the browser. This can quickly get annoying when browsing through dozens of documents. Since most browsers support inline PDF visualizations, I think it would be nice to directly open the PDF in a new tab.

Maybe there is an option to change this behavior but I could not find it.

Originally created by @gdelugre on GitHub (Jan 31, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/126 After searching for a PDF document, the next thing I generally want to do is to open it and read it, without necessarily saving it to on my local machine. However the server returns a ``Content-disposition`` header that makes the file to be downloaded instead of being opened in the browser. This can quickly get annoying when browsing through dozens of documents. Since most browsers support inline PDF visualizations, I think it would be nice to directly open the PDF in a new tab. Maybe there is an option to change this behavior but I could not find it.

kerem added the

wontfix

label

2026-02-27 15:55:09 +03:00

kerem referenced this issue

2026-02-27 15:55:09 +03:00

[GH-ISSUE #125] Spanish language support in defaultLangAnalyzer #126

kerem closed this issue

2026-02-27 15:55:09 +03:00

kerem commented

2026-02-27 15:55:10 +03:00

Author

Owner

@stale[bot] commented on GitHub (Sep 10, 2018):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 10, 2018): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.