1 Answer, 1 is accepted
Hello all,
There is an issue where the font and line-height for the controls in Classic render mode is changed, leading to different size and layout of the components.
We have created a feedback portal item you can follow to get notified when there is any progress on the appearance issue for the controls in Classic render mode. It should be part of the upcoming service pack and it should persist the same appearance as the previous releases.
Also, it contains an attachment that contains the fix .css files for each of the available skins, restoring the font-size, font-family and line-height to the values of the previous release. Loading the files as per the description of the feedback item should resolve the issue.
@Chris, the issue is related mainly to the font, so even with the change, the Menu should have some styles applied. You can check the expected "broken" appearance of the Menu with Classic render mode and MetroTouch skin here:
- Select the Classic render mode radio button: https://demos.telerik.com/aspnet-ajax/menu/examples/functionality/rendermodes/defaultcs.aspx?skin=MetroTouch
If that does not fix your issue please edit your question to include more information, page/menu markup and code-behind, and screenshots of the previous and current appearance or submit a support ticket with the same information.
In the meantime, please ensure there are no JavaScript errors in the browser's console and no failing requests in the Network tab of the browser's DevTools:
Regards,
Peter Milchev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.
Rank 1
Iron
Veteran
Iron
Rank 1
Rank 1
Iron
Veteran
Iron
@Chris, Can you please ensure there is no Mixed render mode issue when you have the Menu and Grid on the page? https://docs.telerik.com/devtools/aspnet-ajax/knowledge-base/common-determine-mixed-render-mode
@Dave, if you increase the selectors' specificity, the !important would not be needed. In your case it is needed probably because you load the styles in the <head> instead of the <body> as explained in the feedback portal item. This is needed because the selector in the fixes and the built-in skins is the same and the built-in styles are loaded programmatically at the end of the <head>, hence overwriting any existing style rule with the same selector.
Rank 1
Iron
Veteran
Iron
Thanks for pointing that out, @Dave. I have updated the feedback portal item to describe that the OrderIndex needs to be set to a big number in order to ensure the loaded file will be after the built-in files: <telerik:StyleSheetReference Path="fixes.css" OrderIndex="99999" />
Rank 1
This is what they told me
"Indeed there is an issue where the font-size for the Classic render mode skins is changed and we will do our best to create some workaround files you can use to restore the previous behavior. They should be useful until we fix the issue in the upcoming service pack.
As this takes some time, could you please share the Skin you are using so we can share with you the skin-specific file when it is ready?"
So no real indication of an actual time frame.