According to the docs, Prisma browser is not listed in the supported browsers for kendo.
Is there a workaround to this?
1 Answer, 1 is accepted
0
Rumen
Telerik team
answered on 16 Sep 2026, 10:27 AM
| edited on 16 Sep 2026, 10:28 AM
Hi Yoadd,
Thanks for the report. Prisma Browser is built on Chromium, so the underlying rendering engine is the same one used by Chrome and Edge, both of which are officially supported. The missing calendar icon is therefore unlikely to be a fundamental compatibility problem with the browser engine itself.
A more likely explanation is that Prisma Browser's built in security layer (DLP, content inspection, or extension policy enforcement) is intercepting or blocking one of the resources needed to render the icon, such as the icon font file, the SVG icon markup, or the theme CSS.
A few things worth checking as a workaround:
Open the browser dev tools (Network and Console tabs) while Prisma Browser is active and confirm that the theme CSS and, if you use font icons, the icon font file are actually being loaded without errors or being blocked by the extension.
Note: Prisma Browser does have developer tools, but access to them is controlled by administrator policy profiles. If dev tools are not available to you, ask your Prisma Browser administrators to enable them so you can troubleshoot the issue: Configure Developer Tools access.
If you are using SVG icons (the default), try switching to font icons instead by setting kendo.setDefaults("iconType", "font") and including the font icons CSS file, since this changes how the icon is delivered to the DOM and can help determine whether the SVG rendering path specifically is the one being affected. Here is a runnable example showing the setup:
Check whether your organization's Prisma Browser policy has any content or script injection rules that could be stripping inline styles or blocking specific asset types, and if so, add an allow rule for your application's domain and assets.
Since Prisma Browser isn't in our officially tested browser matrix, we can't guarantee full support, but because it's Chromium based, the component should generally work once the resource loading issue is resolved. Ensure all required Kendo UI and JavaScript scripts and stylesheets are loaded, as missing resources often cause UI issues.