Microsoft and Adobe partnered to embed Adobe PDF engine into Edge browser.
This new pdf engine can be taken into use from Edge settings, enabling “New PDF Viewer”. The legacy engine in the Microsoft Edge PDF solution is scheduled to be removed in 2025, meaning this “New PDF Viewer” becomes mandatory.
We are using Aspose.PDF as part of Opentext Content Transformations platform. We have noticed an issue with PDF documents created by Aspose.PDF for Java 20.9. When opening PDF document using Edge(New PDF Viewer enabled), the PDF is blank. Document properties are visible and correct, but there is no content. Disabling New PDF Viewer or using newer Aspose.PDF version there are no issues. Of course we could just use newer Aspose version, but we already have thousands and thousands PDF documents created by older version of Aspose, this means we would need to create new renditions for old documents which is huge and time consuming task.
Do you know what could be the problem with older Aspose.PDF and Edges “New PDF viewer”?
We are afraid that we do not have such information at the moment as web browsers have their own configurations and they keep changing them from time to time. We try to keep the API up to date with Adobe Reader standards and follow them. If a PDF generared by Aspose.PDF is unable to load inside Adobe Reader, there may be an issue with the API then.
On the other hand, we can safely assume that Edge might have outdated version of PDF Viewer that didn’t support new standards. If possible, please share both PDF Files i.e. generated using older as well as newer version of the API with which we can do comparison and investigate. We will log an investigation ticket and share the ID with you.
These pdf’s that cannot be opened in Edge are created in customer environment, as far as I know now this does not affect all documents. We are still investigating whether this is actually aspose problem or issue with another plugin, or issue in edge. This was more a question if this is a known issue, but apparrently not. We will continue investigating this issue. Thanks for your effort