Bug on every <ul> element within a RadWindow

[Tommy]

Since last Chrome update version 58 we have visual bugs in ours RadWindow. We found out that it was because of that css class : 

html:first-child .RadWindow ul {
float: right;
border: 1px solid transparent;
}

It is automatically included in the Telerik.Web.UI.WebResource.axd comming from Telerik.Web.UI.Skins.Window.css. We first tough that it was a Chrome bug, but after investigating a little bit more, we realized that chrome was proccessing that css class like it is supposed to. We also found out that firefox is also processing that class the same way as Chrome do. Is there a way to remove that css? 

 

thanks

[John]

I don't work for Telerik and there might be a better solution or workaround, but try using page level style sheet that overrides the CSS values with the !important

Thanks John

[Tommy]

Thanks for the tip John, but I already tried overriding at page level with important. The problem is that I have a lot of RadWindow with <ul> with different float an border. If I try just to override "html:first-child .RadWindow ul " class, I cannot tell CSS to skip the "float : left" attribute and take the next one with a lower priority.

[John]

Yes it sucks when you have a bunch of anything that might require some manhandling.

Hopefully they can provide a fix or an official workaround.

You also might want to try some of the other render modes of the skin perhaps they are good.

If something like this below doesn't work perhaps try another skin until you hear something back from Telerik.

<style type="text/css">
    html:first-child .RadWindow ul > :first-child {
float: left !important;
}
</style>

[Marin Bratanov]

Hi guys,

That's a known issue caused by FF52 and Chrome 58 reading old selectors differently and it is fixed in R2 2017. You can find workarounds in this page: https://feedback.telerik.com/Project/108/Feedback/Details/213969-uls-in-radwindow-float-to-the-right-under-firefox-52-and-chrome-58. The Lightweight RenderMode does not exhibit this issue as well, so that may be another option for you if a CSS override is not suitable for your case.

Regards,

Marin Bratanov
Telerik by Progress