In the Word rendering, there is sometimes space between the footer and the body of the document.

Bindings to the TitleStyle property of a ToC section result in the following error:

 Bindings error - The value of property 'TitleStyle' is null

It takes 2+ seconds between "info" polls to the server. This should be a much smaller interval. Maybe .5 or .25 seconds.

Telerik's own ReportClient example shows a 500ms interval between info polls...

        private static byte[] GetDocument(ReportClient restServiceClient, string instanceId, string documentId)
        {
            bool documentProcessing;
            do
            {
                Thread.Sleep(500);// wait before next Info request
                documentProcessing = restServiceClient.DocumentIsProcessing(instanceId, documentId);
            } while (documentProcessing);

            byte[] pdfDocumentBytes = restServiceClient.GetDocument(instanceId, documentId);

            return pdfDocumentBytes;
        }

In some cases, the textbox width will be nearly but not enough to fit the whole string and as a result, the textbox will grow and will thus push the items below it further down.

In Page Sections, this may even result in some of the items that are near the bottom not being displayed at all.

It would be great if there was a warning when the width is not enough so that such scenarios are avoided.

There should also be an option to disable the warnings.

If you add the 'kendo.common.min.css' that is required for the Html5 Viewer to the page with the Web Report Designer, the latter Menu styles get broken.

Due to this, if you need to have both the viewer and the designer in the same project and cannot have scoped styles, the appearance of one of them will be broken.

Consider adding functionality that allows for loading Assets into the Asset Manager from code. 

I would prefer to store assets in a database and load them up for a user.

Makes more sense than randomly loading them from whatever computer you are working on.

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

Currently,  you can select multiple report items with the CTRL when you run the Web Report Designer on Mac, however, this is interpreted as a right-click. Please, check the attached video.

The correct behavior should be by using CMD.

Steps to reproduce the problem:

Using the Default or Material Kendo Theme (v5.6.0) with the Telerik HTML5 Report Viewer, the Boolean parameter which uses a Checkbox for it's display, is not visible (this may affect other themes as well).

I confirmed an older version v4.40.0 has a height and width set for the k-checkbox CSS class as such:

https://unpkg.com/@progress/kendo-theme-material@4.40.0/dist/all.css

.k-checkbox {
    border-radius: 2px;
    margin: 0;
    padding: 0;
    width: 16px;
    height: 16px;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    box-sizing: border-box;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

while the latest v5.6.0 does not:

https://unpkg.com/@progress/kendo-theme-material@5.6.0/dist/all.css

.k-checkbox {
    margin: 0;
    padding: 0;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    flex: none;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

The checkbox is actually on the page, but is so small it's basically invisible and completely unusable, requiring a manual CSS override to fix.

When exporting to PDF from Telerik Report Designer the software creates a list of flat links for each TOC entry, but the links are separated in the structure from the TOC Label. While a good start, it would be better to use a main TOC tag under which each line in the TOC would receive a TOCI (Table of Contents Item) tag. Each TOCI would contain the label and link for the respective item. Attaching a few examples to assist.

References:

https://www.hhs.gov/sites/default/files/pdf-tagging.pdf (page 29).

https://www.pdflib.com/pdf-knowledge-base/pdfua/the-pdfua-standard/ 

When exporting the tags for the document's Table of Contents Telerik Report Designer exports TOC leaders as distinct tags, requiring that they be removed when completing the accessibility tagging for the document. Leaders - the ellipses found in the Table of Contents (e.g., Introduction ...................... Page 3) between the TOC item and the page number will be read by assistive technology as "dot dot dot dot dot..." etc. They need to be deleted from the tag tree. Please Artifact them or (preferably) NOT tag them on the export. Thanks.

Reference: 

https://www.levelaccess.com/pdf-table-of-contents/

https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/pdf.html