This is a migrated thread and some comments may be shown as answers.

How to avoid my app talking back to Telerik.

1 Answer 50 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Steve asked on 19 Jul 2018, 09:56 PM

Due to this message in Chrome...

"The SSL certificate used to load resources from https://www.telerik.com will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information."

I now know the Kendo-UI tries to talk back to Telerik, for at least a CSS file, but I don't know what else.

Many of our customers have a white-list of allowed internet sites, and we don't want our application to require random 3rd party addresses to be white-listed on their firewalls, or have our request refused. Architecturally, we did not appreciate this requirement for remote files for a library that we thought we hosted and delivered ourselves.

What are the options for not requiring internet access to use the Kendo UI? Is it just a CSS file (or other CDN files) or other things like metrics reporting? The CSS file does not appear to relate to any given version of Kendo UI - how do you keep backwards compatibility?

Many thanks for your help.

1 Answer, 1 is accepted

answered on 23 Jul 2018, 12:17 PM

Hi Steve,

Indeed, some versions of the Kendo themes relied on loading the TTF files required for the PDF export functionality, from our CDN. This is now fixed, so you can safely upgrade to the latest version of our theme that does not rely on external loading of these resources:

https://www.telerik.com/kendo-angular-ui/components/styling/theme-default/changelog/#toc-bug-fixes (fixed in version 2.52.2).

There are no specific versions of the theme related to any other package's specific version - all our packages follow its own lifecycle and the latest versions of all packages contain all latest fixes and enhancements (this is why we recommend updating these versions regularly).

Typically, when an issue/bug is found, we determine whether it is a styling issue that can be fixed in the theme package, or a component-specific issue that needs to be fixed in the respective package. This is why there is no correlation between the versions of the components' packages and the theme one.

Let us know if you have further questions.

Regards,
Dimiter Topalov
Progress Telerik

Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.