Context:
- Playwright Version: 1.2.1
- Operating System: Mac
- Node.js version: 12.14
- Browser: Chromium
Describe the bug
When navigating to PDF that is delivered with the header Content-Disposition: inline, Playwright opens in a new page and uses the embedded Chromium PDF viewer.
From this point it's impossible to get the actual PDF content. Even when inspecting the response event, the actual response object's body only contains the HTML presenting the embedded viewer with an inline ID representing the PDF.
Whilst I'm sure there are some situations that would warrant the in-browser PDF viewer being turned on, I would guess that having these download by default would be the more common use-case within Playwright.
Context:
Describe the bug
When navigating to PDF that is delivered with the header
Content-Disposition: inline, Playwright opens in a new page and uses the embedded Chromium PDF viewer.From this point it's impossible to get the actual PDF content. Even when inspecting the
responseevent, the actualresponseobject's body only contains the HTML presenting the embedded viewer with an inline ID representing the PDF.Whilst I'm sure there are some situations that would warrant the in-browser PDF viewer being turned on, I would guess that having these download by default would be the more common use-case within Playwright.