After upgrading Web dll's from version 2012.n to 2015.n the CSS property for the tristate.png is being set to incorrect values regardless of the .rtChecked, etc values are being set to (and have been set to). The values in the TreeView.css file are:
.RadTreeView .rtChecked { background-position: 0 0; }
.RadTreeView .rtUnchecked { background-position: 0 -13px; }
.RadTreeView .rtIndeterminate { background-position: 0 -26px; }
The values are being overridden from the now being set to:
.RadTreeView .rtChecked { background-position: 0 -40; }
.RadTreeView .rtUnchecked { background-position: 0 0; }
.RadTreeView .rtIndeterminate { background-position: 0 -80px; }
The dom explorer (in IE) is saying that this setting is held in the WebResource.axd file, which is a file dynamically created by the runtime.
Does anyone have any idea where these background-positions values are being set from so I can correct it, or help me understand what happened during the upgrade that caused these settings?
Thank you!
Jason
5 Answers, 1 is accepted
Regarding to developing and improving our controls, we have changed sprites and modified background positions as well. If you upgrade to the new version, it is necessary to modify custom sprites according our new sprites, or overwriting CSS rules with new background positions. We apologize for the inconvenience caused.
Regards,
Magdalena
Telerik
Rank 1
Maybe I'm missing something, but if I upgrade, and the programming changes to use different sprites, then why weren't the new sprites installed?? I'm completely baffled by that. Modifying the treeview.css, doesn't help, such as using the !important directive.
The fix I employed was just to disable using the skin altogether. Then the Telerik resource respect the treeview.css file. Ridiculous.
We have updates also the sprite image. The conflict causes if you are using your own custom sprite instead of our inbuilt and in the same time you do not disable our updated inbuilt base files with the EnableEmbeddedBaseStylesheet="false".
We are sending you a sample project, where we simulate a scenario with using old sprite as a custom image. In the project we are overwriting our base styles our background positions.
Regards,
Magdalena
Telerik
Rank 1
When did I say we're using a custom sprite? We're using the same one you just sent in your code example. So doesn't that prove we are using a sprite from Telerik, which by definition means it's not custom? This should be a really simple problem. I fixed it by disabling the custom skin and using the default EnableEmbeddedBaseStylesheet = true so it uses the TreeView.css file.
Now, I'm not the original author of this code, nor am I an expert in Telerik's world, but it seems to me that if you wanted to help a customer, your focus should have been on where the image file is that matches the css that the Telerik installer seems to have updated somewhere for the custom skin (see above for those background-position values). I looked for an image file that would match that new css but I can't find one. We're now just using the original Telerik image, as usual with the base skin as the solution since it seems the upgrade broke the custom skin. I hope this helps the next guy. Sorry, but after this many days for a simple problem, this thread is a failure.
All styles and images that are not inbuilt and are applied additionally, we call them "custom". Even if they are copy of our inbuilt resources. The reason is that these resources cannot be updated by us. When we update our inbuilt images, we update also their background positions. If you are applying a sprite additionally, it is not updated along with our resources.
If you would like to update the sprite following our inbuilt images, you can find it in the "Skin" folder of our assembly. Common sprites used in more controls are in the "Common" folder. Other sprites are placed in folders named by controls which used the sprite.
Regards,
Magdalena
Telerik