Sprite image overlay with custom theme

[Erik]

Probably I am doing something wrong and hopefully a simple fix - I am seeing the up triangle sprite overlaid on all sprite images when using a custom theme.  As seen here.

I had gone through the process of creating a custom theme based off of material through here. In the generated kendo.custom.css file, I replaced all references to images (url('none/sprite.png'); with the proper path on my web server.

Everything looks fine with standard material theme:

<link href="https://kendo.cdn.telerik.com/2017.3.913/styles/kendo.common-material.min.css" rel="stylesheet" type="text/css" />
<link href="https://kendo.cdn.telerik.com/2017.3.913/styles/kendo.material.min.css" rel="stylesheet" type="text/css" />

 

But the sprites become overlaid after I specify my custom theme:

<link href="https://kendo.cdn.telerik.com/2017.3.913/styles/kendo.common-material.min.css" rel="stylesheet" type="text/css" />
<link href="../../Content/kendo.custom.css" rel="stylesheet" type="text/css" />

 

[Orlin]

 

Hello Erik,

The icons overlayed with sprites are related to this issue: https://github.com/telerik/kendo-ui-core/issues/2696

To work around it, please replace all instances of url('none/sprite.png') with none in the CSS file, and this should fix the icons for you.

I hope this helps, and do let us know if you need further assistance with this.

Regards,
Orlin
Progress Telerik

[Erik]

Orlin, changing all of the sprite url calls to just "none" did resolve the problem.  Though I am unclear if that is a final solution.

The github issue tracker link you posted is exactly what I tried to resolve by changing the url('none/sprite.png') to the path of my theme.  Is that no longer required? If so then why hasn't the theme generator been fixed to not output those 'url's?

[Orlin]

Hello Erik,

The sprite file is a remnant from before the Kendo UI widgets switched to using font-based icons earlier in the year, so it is no longer needed. Removing any reference to it is a workaround to the issue I sent you. Once we have it resolved, the Github issue will be closed, and a general fix will be available with the next official release.

I hope this answers your questions.


Regards,
Orlin
Progress Telerik