Hi,

You will need to follow these steps:

1. Handle NewWindow event and accept this new window. You MUST accept the new window in order for the loader to continue loading the PDF file. If you do not accept the new window, the request dies here. See here for more information on how to accept the new window:

https://www.essentialobjects.com/doc/webbrowser/advanced/new_window

This also means that you MUST create a new UI to host the new WebView. It can be a temporary window that you close/hide later;

2. Handle ShouldForceDownload event of the NEW WebView. Since it's the new WebView that will load the PDF file, you should handle ShouldForceDownload on the new WebView. You should also handle all download related event on that WebView;

3. Once the download starts on the new WebView, you can hide the window you created in step 1;

4. Once the download completes on the new WebView, you can destroy the window you created in step 1;

It's possible to create an invisible window on step 1 so that you don't have to hide it later. For example, you can create a window with size (0, 0), or create set its location to be outside of screen (with negative left/top value).

Hope this helps. Please feel free to let us know if you have any more questions.

Thanks!

Hi Stefan,

I am not sure what object is your chromiumWebBrowser, so we can't verify whether your code is correct or not. If you still have problems, you can try this two step process:

Step 1: Handle NewWindow event properly

Make sure you can DISPLAY the new PDF first. This means handling NewWindow event and let the PDF file load normally. Inside your NewWindow event you need to create your host UI (for example, a new tab that loads the PDF file). You should NOT call WebView.Navigate to load the PDF file. See here for more information on how to handle NewWindow event:

https://www.essentialobjects.com/doc/webbrowser/advanced/new_window

It is extremely important that you handle NewWindow event correctly first. Nothing is going to work if you don't get this step right;

Step 2: Change the behavior from displaying the PDF file to downloading

This step involves handling ShouldForceDownload event. Inside this event handler you can check your Url and set e.ForceDownload to true. Everything on this step is on the new WebView, not on the original WebView.

Once you get these two steps working, you can review the step by step instructions in our original reply to get the rest working.

Hope this helps.

Thanks!

Great. Glad to hear that the issue is resolved!