ReportViewer will resize correctly when the window is resized by manually dragging the frame, but when 'Maximize' or 'Restore Down' buttons are used, the resize will not occur. 

If continues scrolling is turned on, the next page to load in will be in a different size because it will be in the correct size, while the first page remains in the previous size.

A work-around is to add this codesnippet to the HTML, which will trigger the resize:

function resizeViewer() { $("#reportViewer1").trigger('resize'); }
window.addEventListener("resize", resizeViewer);

On numerous occasions I've found that the need to float or rearrange the designer windows such as the data explorer, properties or group explorer window would be very beneficial to my workflow.

As well this request should consider the ability of the data explorer and report explorer to be decoupled so as both can be visible simultaneously.

Normally table's of context are formatted with roman numerals.  Based on the responses in the forum, only Arabic numbers are allowed.  Request the ability to change the formatting of the rule numbers and restart the page numbering after the TOC.

Generate and distribute packages built against .Net 5.0.

Currently .Net 5.0 RC1 and .Net 5.0 RC2 are announced. The official version has been announced on 10th of November.

For our Customers a major drawback to creating form type reports (Invoices, Purchase Orders etc.) using Telerik Reporting is the inability to show vertical dividing lines between data columns in the 'Detail' section of the report that extend all the way down the page to the Page/Report footer. We were able to do this with Crystal Reports. But we plan to migrate all our Crystal reports to Telerik.

When configuring a WebServiceDataSource in the Web Report Designer in ASP.NET,  upon previewing the data there is an error '404 Not Found". The same web service was successfully resolved by the Standalone designer and in the ASP.NET Core demo.

The data source fields were visible and usable in the designer also under ASP.NET Web Report Designer.

When a Report with ObjectDataSourceParameter is loaded into the WebReportDesigner, the designer throws an error when trying to initialize the parameter.

Could not create instance of 'ObjectDataSourceParameter'. TypeError: Cannot read property 'push' of undefined
    at new d (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:89908)
    at new a (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:277743)
    at s.CreateInstance (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:644848)
    at d.<anonymous> (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:515470)
    at Generator.next (<anonymous>)
    at http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:513964
    at new Promise (<anonymous>)
    at l (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:513709)
    at d.CreateComponent (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:515160)
    at a.<anonymous> (http://localhost:23456/api/reportdesigner/designerresources/js/webReportDesigner-14.2.20.1021.min.js/:9:58884) 

When a report is rendered by the REST Service, and that report has an element with applied 'Navigate To Report'-action, the full path of that file is being used as a reference, instead of a relative path or just the report-name.

Hello Team,

I will be great if the Telerik Reporting REST Service Core could support System.Text.Json serialization.

Best Regards,

Feature Request - Show email sent / error notification using the report viewers built-in notification system. 

It would be nice to have an option to have a message shown when the email with the report is sent or if there was an error sending.
Right now when you hit email and send the user does not know if it was successful or not. Being async is nice but I have noticed that it could take a few seconds to complete and if the user navigates away from the report viewer during this time the report has the possibility of not sending. Either way right now the user has no definitive method of knowing if the email was sent or not.