Groupdocs viewer (8.1.3) - Problems with print loader popup

GroupDocs.Viewer Product Family
,
1

Hi, Please find below issues observed on 8.1.3. These are related to the print loader popup that indicates no of pages loaded.

  1. Popup stuck at “Loading 2 of 180 pages” when PreloadPages = 1.
    To reproduce - just click too fast on print button as soon as the button appears on page refresh. please find attached recording below.
    Stuck_PrintPreview_1PreLoadPageCount - Copy.zip (555.7 KB)

  2. Close Popup and ones it’s closed click Print button again.
    Popup is closed but after clicking on print it doesn’t open again. I think this can be easily reproducible.

The issues may be there on older version as well, just noted on 8.1.3, as i observed.

Thanks.

2

@vladimir.litvinchik - fyi. just creating separate ticket so we can track this. These are not blockers but good to get fixed. Thank you.

3

@sachinerande

Thank you for the quick feedback. I have reproduced both issues and reported to the responsible team. The issue ID is VIEWERNET-5623.

1 Like
4

@sachinerande

Both issues were fixed in the latest package version 8.1.4. The issue origin was conflicting logic related to loading pages and preparing print preview.

5

Thanks @vladimir.litvinchik. I have checked and issue 1 appear to be fixed.
Issue 2 appears to be still there, if you would like to repro just add some middleware like below that adds delays for request processing, and then try repro.

app.Use(async (context, next) =>
{
    if (context.Request.Path.ToString().Contains("viewer-api/get-page"))
    {
        await Task.Delay(5000);
    }
    else if (context.Request.Path.ToString().Contains("viewer-api/create-pages"))
    {
        await Task.Delay(5000);
    }
    await next(context);
});

Steps to repro issue 2.

  1. Click print button, that shows popup (indicates no of pages loaded or preparing to print)
  2. Immediately close popup and click print button again.

Observation - no popup window is shown, but after sometime, the print preview window appears.

6

@sachinerande

Using your code and steps I reproduced the issue and reported it to the responsible team. Will update you when I have any information.

7

@vladimir.litvinchik Great, Thank you!