Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adobe integration question: Will WebView2 PDF rendering change? #3205

Closed
JensMertelmeyer opened this issue Feb 9, 2023 · 9 comments
Closed
Assignees

Comments

@JensMertelmeyer
Copy link

According to
https://blogs.windows.com/msedgedev/2023/02/08/adobe-acrobat-microsoft-edge-pdf/
and
https://techcommunity.microsoft.com/t5/microsoft-edge-insider/microsoft-edge-and-adobe-partner-to-improve-the-pdf-experience/ba-p/3733481

it is said that

we are natively embedding the Adobe Acrobat PDF engine into the Microsoft Edge built-in PDF reader, with a release scheduled in March 2023 (...) the legacy engine in the Microsoft Edge PDF solution is scheduled to be removed on March 31st, 2024

and especially

Visually, users will see an unobtrusive Adobe brand mark in the bottom corner of their PDF view. These users will also see an option to try the advanced features, such as converting PDFs, combining files, editing text and images. (...)

My question: Since it is already planned to entirely remove the existing PDF rendering from Edge, will that also affect WebView2?

@eneiner
Copy link

eneiner commented Feb 9, 2023

I was going to ask the same question. Is the current webview2 pdf rendering going to replaced by Adobes rendering engine?

@rd53hu
Copy link

rd53hu commented Feb 12, 2023

Any answer to this. My company is evaluating webview2 for pdf intgration at work.

@champnic
Copy link
Member

Hey all! Apologies for the delay here while we confirmed some details. The WebView2 control will continue to use the built-in PDF Viewer by default, not the Adobe viewer. You will continue to see the same PDF rendering behavior and UI controls. There should be no Adobe branding within the WebView2.

We're still working through the plan post-March 31st, 2024, when Adobe viewer is scheduled to become the default everywhere and the enterprise opt-out is removed. We'll reach out when we have more info the share. Thanks!

@JensMertelmeyer
Copy link
Author

Dear @champnic ,
half of the time until "end of March 2024" has now passed. Are there any updates or something we can start preparing for?

@Danielx64
Copy link

@JensMertelmeyer

I just found this:

How will this change affect WebView2 users and applications?

The PDF experience for WebView2 users will be at parity with the current Microsoft Edge built-in PDF reader. The option to access paid Adobe Acrobat premium features will not be visible in the new PDF experience on WebView2. The unobtrusive Adobe brand mark will also not be visible in WebView2.

@JensMertelmeyer
Copy link
Author

Yes, this is how WebView2 users are currently affected (meaning: not at all), until end of March 2024.

The question is: What will happen after that?

Right now, it sounds like the current PDF engine will be removed entirely, and no longer be accessible from WebView2. There is no announcement for what will happen in a few months.

@victorhuangwq
Copy link
Collaborator

@Danielx64's answer is the current statement for will be happening

How will this change affect WebView2 users and applications?
The PDF experience for WebView2 users will be at parity with the current Microsoft Edge built-in PDF reader. The option to access paid Adobe Acrobat premium features will not be visible in the new PDF experience on WebView2. The unobtrusive Adobe brand mark will also not be visible in WebView2.

https://techcommunity.microsoft.com/t5/microsoft-edge-insider/microsoft-edge-and-adobe-partner-to-improve-the-pdf-experience/ba-p/3733481

@victorhuangwq
Copy link
Collaborator

Closing this issue as it has been addressed.

@JensMertelmeyer
Copy link
Author

Follow-up information available at

MicrosoftEdge/WebView2Announcements#81

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants