Groupdocs viewer not properly displaying PPTX files containing SVG files

GroupDocs.Viewer Product Family
1

Hi,

We are having an issue with PPTX files not displaying properly when an SVG file is included in the PPTX. The display renders the first SVG file it finds and not the PPTX file.

If i save the PPTX files down to an older Powerpoint version (PPT) the file displays correctly with the SVG files showing.

When i use the Groupdocs online viewer with the PPTX files they display correctly.

We are wondering if maybe your online viewer is different than what we are using which could be the cause.

See attached documentation for our testing results from our system and your online viewer. I can’t upload the Powerpoint files.

Powerpoint Testing on DAM.docx (488.6 KB)

These are the Groupdocs versions we are using

  • “GroupDocs.Conversion” Version : 23.8.0,
  • “GroupDocs.Viewer.UI” Version : 6.0.15,
  • “GroupDocs.Viewer.UI.SelfHost.Api” Version : 6.0.16,
  • @groupdocs.examples.angular/viewer Version : ^0.8.100
2

Hello CMorton!

Thank you for being interested in GroupDocs.Viewer and for sharing such detailed report!

  1. Unfortunately, we do need these test files in order to reproduce the described issues on our side. Please upload the “CM_TEST_FILE***” sample files which you have mentioned in the “Powerpoint Testing on DAM.docx” report to some cloud storage on your choice and share the link with us.

  2. Regarding the difference between the GroupDocs.Viewer App and the GroupDocs.Viewer.UI, there are two main distinctions:
    2.1. By default GroupDocs.Viewer.UI renders the input documents to the HTML format, while GroupDocs.Viewer App - to the images (PNG in particular), so for the complex documents the results may be different. Please try to switch the rendering mode to the PNG in the GroupDocs.Viewer.UI and see the results.
    2.2. GroupDocs.Viewer App uses new Angular UI, which will be also applied to the GroupDocs.Viewer.UI in the nearest future.

In order to enable the PNG rendering mode in the GroupDocs.Viewer.UI, please add the config.SetViewerType(GroupDocs.Viewer.UI.Core.ViewerType.Png) call to the AddGroupDocsViewerUI and AddGroupDocsViewerSelfHostApi, as shown below:

builder.Services
        .AddGroupDocsViewerUI(config => {
            config.SetViewerType(GroupDocs.Viewer.UI.Core.ViewerType.Png);
        });

builder.Services
        .AddControllers()
        .AddGroupDocsViewerSelfHostApi(config =>
        {
            config.SetViewerType(GroupDocs.Viewer.UI.Core.ViewerType.Png);
        })

Thanks!

3

Thanks for getting back to me Denis.

Here are links to the PPTX files that we are having the display issues with.

CM_TEST_FILE.pptx - DCM - ASMBL

CM_TEST_FILE_Airplane-PNG.pptx - DCM - ASMBL

CM_TEST_FILE_Airplane-SVG.pptx - DCM - ASMBL

Here are the links to the PPT files that display correctly in our Viewer

CM_TEST_FILE.ppt - DCM - ASMBL

CM_TEST_FILE_Airplane-PNG.ppt - DCM - ASMBL

CM_TEST_FILE_Airplane-SVG.ppt - DCM - ASMBL

Also, for the statement below, do you have an idea as to when it will be applied? Is it days, weeks or months?

2.2. GroupDocs.Viewer App uses new Angular UI, which will be also applied to the GroupDocs.Viewer.UI in the nearest future

Thanks,
Craig

4

Hello Craig!

Thanks for sharing the files, we’ll starting to investigate them now.

Regarding your question about the terms: we plan to release a new Angular UI front-end for the GroupDocs.Viewer.UI till the end of this month.

With best regards,
Denis

5

Hi,

We had noticed the inconsistencies using HTML and are already using the PNG converter. Please see attached to validate everything is ok but it seems to be the same code you have suggested.
How likely it is that the Angular UI update fixes this issue? It feels it is a more “core” problem so we are wondering whether we should be investigating other possible differences. For instance, do you know on which operating system your demo app runs? Our viewer runs on Ubuntu, maybe yours runs on Windows? In theory both are supported but maybe GroupDocs behaves differently depending on the OS?
Current settings for PNG

6

Hi Craig!

Sorry for the long delay.

First of all, regarding the attached files, We’ve investigated all of them and unfortunately we were unable to reproduce the described issues. All files, including CM_TEST_FILE.pptx and CM_TEST_FILE_Airplane-SVG.pptx, are rendered correctly by the GroupDocs.Viewer.UI. The airplane image is shown correctly in both main window and slide preview panel.

We’ve compared it with MS PowerPoint 2021 as a reference - all is matching.

We’re attaching four screenshots of two reported problematic documents: the first was taken is from MS PowerPoint, second - from Viewer. On the 4th slide all is matching - image, text desciption, background, etc, same for preview panel.

We’ve checked all of these using the original ‘GroupDocs.Viewer.UI’ solution from the GitHub, to be precise, we used a sample project ‘GroupDocs.Viewer.UI.Sample’.

We want to help you and thus we need to start from some common basis in order to dig deeper. So please check it on your side and tell us the results. Do not perform anything special, just download the solution from GitHub, open in Visual Studio, make the GroupDocs.Viewer.UI.Sample to be a startup project, and launch locally. Then navigate to the “\viewer” page and drag-and-drop the CM_TEST_FILE.pptx and/or CM_TEST_FILE_Airplane-SVG.pptx on it, and tell (and show) us the results.

For example, maybe, it is an OS-related issue, because you’ve mention that you’ve run it on Ubuntu, while we’re using MS Windows for development.

Regarding your question about on which operating system the Viewer demo app runs - it runs inside the Docker container, where Debian is installed.

Thanks!

File_Airplane_SVG_PPTX_local_PowerPoint.png (191.0 KB)
File_Airplane_SVG_PPTX_local_ViewerUI.jpg (199.4 KB)
File_PPTX_local_PowerPoint.jpg (219.3 KB)
File_PPTX_local_ViewerUI.jpg (149.5 KB)

7

@CMorton

Have you managed to fix this issue or you still experience the same problem?

8

@vladimir.litvinchik Yes, it appears we have fixed the issue at this time. Thanks for your assistance.

9

@CMorton

Great, thank you for the feedback! Could you please share what the fix was on your side?