Hi Bo Johansen,

I indeed agree with you that there are some TagHelper that are currently lacking the "html-attributes" configuration. This would be a fairly large initiative in order to assess whether the majority of component could employ this configuration and there are no potential drawbacks.

Your feedback here is indeed valid, and I personally agree with you that such a feature would indeed be helpful to the community.

We will monitor this item in order to see the community's interest.

Kind Regards,
Alexander
Progress Telerik

Hi Bo Johansen,

I hope you are doing well!

Generally, the majority of our controls expose their own .HtmlAttributes() API configuration which allows you to deliberately place arbitrary HTML attributes to the elements that wrap together the component. In the context of the TreeList, this would look something like the following:

<style>
    .smallTreeList {
        width: 50%;
    }
</style>   
 
@(Html.Kendo().TreeList<EmployeeDirectoryModel>()
    .Name("treelist")
    .Columns(columns =>
    {
        ...
    })
    .HtmlAttributes(new {@class = "smallTreeList"})
     ...
)

In cases in which the style rules are not applied, there may be some selectors coming from the themes with higher specificity. This can be circumvented by explicitly placing the !important property. I personally use this as a rule of thumb when I try to override existing classes.

That being said some of the controls offer setting HtmlAttributes through other configurations as well. Thus, my personal recommendation here would be to use the server-side API as a navigator, so to speak.

Additionally, I would also recommend the following blog post when it comes to inspecting existing elements in the DOM:

• Improve Your Debugging Skills with Chrome DevTools (Blog Post)

Here is a Telerik REPL example that showcases the aforementioned snippet:

• Telerik REPL for ASP.NET Core Example

I hope this proves helpful.

Kind Regards,
Alexander
Progress Telerik