There was no mention of this in the release docs.
I have to say I consider changes to things like colours and fonts at least as important as changes to functionality and, therefore worth of note in the docs.
You may consider it a petty complaint, but end-users get really up-tight about things like this if they're not forwarned, and as I have to explain these changes to those further up the food chain internally, it'd be nice to get some advance warning.
7 Answers, 1 is accepted
We are in a process of migrating CSS into SASS. During the process some of the CSS selectors were changed and they specificity is heavier now. In the case of Splitter Sitefinity skin (I suppose this is the sking you are using, as you didn`t mentioned in your post) the Segoe UI style coming from the Base CSS is was not overridden by Arial.
We are aware of the issue and fix will be availbe in the next official release and in the next internal build also.
During the migration some of the background, text and border colors will be changed to match its skin color scheme as now there are some differences between the controls for similar elements.
For now, you could use the following fix:
the Telerik team
Thanks for the reply.
You are right in that I didn't metion the skin I was using. The changes I noted were in the Office2007 skin.
I note your comments about the upcoming fixes and look forward to seeing them. I also note your suggested workaround.
it is strange as all predefined skins are using Segoe UI as default skin, except Sitefinity which default font is Arial, and Transparent, which is Tahoma.
Are you sure, that Office2007 that you are using is with Arial? It is possible if you did some CSS overrides, and now because the specificity is higher and the overrides not to work already.
If this is the case, you need to add some extra tag or class to the CSS cascade in order to increase the specificity and to make the override work.
the Telerik team
Facing the similar issue with Office2007 skin after upgrading (from 2011) to 2015 Q3. The font family and size of the body CSS is getting overridden with Radsplitter CSS.
Also I tried replacing the body CSS with body id and class but still its getting overridden by Radsplitter css in both the cases. Please suggest how to fix this.
All styles applied to the Splitter are cascaded through its own CSS class and should not affect the other styles on the page. Actually, if you are setting global styles on the page holding the Splitter it will most probably inherit them as they will affect its child html elements.
I am attaching a sample page demonstrating that - are you experiencing the same problem with it?
Thanks for the information. In the example you shared, do you try to mean all the child elements inside the RadSplitter will inherent the CSS of RadSplitter instead of body.
In my case, RadSplitter CSS is overriding the parent css (in my case the body). I resolved the issue by applying the new CSS class with same font details to the child elements inside RadSplitter. However this issue never occurred while using the telerik web version 2011.2.712.35.
Please, excuse me by not being clear enough in my previous reply. If there are styles set to the the body, they will be applied also to the elements of the Splitter.
If this does not happen in your project, can you elaborate a bit on the exact scenario in which which this behavior occurs?
- Which version of the controls are you using now?
- Do you experience the reported problem in all browsers or only in a specific one?
- Can you send us an isolated project replicating the case so we can examine it on our side?