![]() The HTML5 Report Viewer requires HTML5 compliant browser with support for JavaScript 1.8.5 (ECMAScript5) and CSS3. The TreeView is in Kendo UI Professional. All widgets except the TreeView can be found in Kendo UI Core. The Touch widget is required only for the gestures. Note that the widgets have other dependencies. In case you edit the template and remove a widget you can subtract it from this list as well. There are two ways to create a custom build - with Kendo UI Custom Download Builder and using gulp build tool.īelow you can find the list of widgets that the HTML5 Report Viewer requires in order to work properly. Since the HTML5 Report Viewer uses Kendo UI for its default template it is possible to use it even with a custom build instead of using the shipped Kendo bundle. If you want to make sure that there are no Internet connection problems and the CDN service cannot be reached for some reason, download the content of the JavaScript file (open in the browser that does not support promise natively, for example, IE) and serve it as a local JS file. For example you can load locally the same polyfill we use: In this case, you should load a Promises/A+ JS implementation of choice into your application. If the browser security does not allow dynamic script loading or the client computer has no internet access, the CDN script might fail loading. If Promise object is not detected, the viewer will try to load a Promise polyfill from Polyfill.io as CDN. Most modern browsers have native implementation and support for this object (see Browser Compatibility at Promise - JavaScript | MDN). The viewer depends on the Promise object and will not load successfully if it is not available. For more details, check Styling and Appearance. The HTML template includes links to the HTML5 Viewer's CSS template file and icon fonts, also available through the resources of the HTML5 Viewer. ![]() If you will not add changes in the default template, you do not have to specify the HTML template viewer option.If you use a CDN to load the required CSS and JS files, verify the links are run over HTTP or HTTPS depending on the hosting of the application.For more information how the final page should look like, check the last step of Manual Setup article. If no Kendo widgets are utilized in the page the report viewer will automatically register a custom Kendo subset to enable the required Kendo widgets. The report viewer JS should be referenced after any other Kendo widgets or bundles.jQuery must be loaded only once by the page with the HTML5 Viewer.The required CSS and JS files must be loaded before creating the HTML5 Viewer widget on the page.The HTML5 Viewer is designed to request its HTML template, HTML5 Report Viewer widget implementation and Kendo UI widgets subset from the resources of the Reporting REST Service.Important Settings while configuring HTML5 Report Viewer page For more information see: Browser Support. By default, the subset is served from the Telerik Reporting REST Service. For more information refer to Telerik Reporting License Agreement (point 4.2). Telerik Reporting provides a JS file containing a subset of the used by default Kendo UI widgets called telerikReportViewer.kendo-17.0.23. Kendo UI Professional license is not required if you are only going to use the default widgets by the HTML5 Report Viewer. By default, it is served from the Telerik Reporting REST Service. ![]() Reference to HTML5 Report Viewer JavaScript called telerikReportViewer-17.0.23.Note that the jQuery slim build is not supported. As the HTML5 Report Viewer uses Kendo UI widgets, conform the jQuery version according to the Kendo UI requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |