When you have a button inside a MultiSelect Footer template (for example), it is different visualized compared to the same button outside of the component. This comes from the k-list-container that is applied when a button is inside a toolbar.

-------ADMIN EDIT---------

A possible workaround for the scenario is to use custom styles as shown below:

<div class="row">
    <div class="col-2">
        <TelerikButton ButtonType="Telerik.Blazor.ButtonType.Button"
                       Icon="k-icon k-i-add"
                       Primary="true">
            New Value
        </TelerikButton>
    </div>

    <div class="col-10">
        <TelerikMultiSelect Data="@(
                                            new List<SelectListItem>()
                                            {
                                                { new SelectListItem { Text = "Text 1", Value = "Value1" } },
                                                { new SelectListItem { Text = "Text 2", Value = "Value2" } },
                                                { new SelectListItem { Text = "Text 3", Value = "Value3" } },
                                                { new SelectListItem { Text = "Text 4", Value = "Value4" } }
                                            })"
                            FilterOperator="StringFilterOperator.Contains"
                            Filterable="true"
                            TItem="SelectListItem"
                            TValue="string"
                            TextField="Text"
                            ValueField="Value">
            <FooterTemplate>
                <TelerikButton ButtonType="Telerik.Blazor.ButtonType.Button"
                               Class="my-nested-button"
                               Icon="k-icon k-i-add"
                               Primary="true">
                    New Value
                </TelerikButton>
            </FooterTemplate>
        </TelerikMultiSelect>
    </div>
</div>

@code{
    public class SelectListItem
    {
        public string Value { get; set; }
        public string Text { get; set; }
    }
}

<style>
    .k-list-container .k-button.my-nested-button {
        background-color: #ff6358;
        align-items: flex-start;
        align-self: flex-start;
    }

    .k-list-container .k-button-primary.my-nested-button,
    .k-list-container .k-button.k-primary.my-nested-button {
        /*copy the colors from the basic button*/
        border-color: #ff6358;
        color: #ffffff;
        background-color: #ff6358;
        background-image: linear-gradient(rgba(0, 0, 0, 0), rgba(0, 0, 0, 0.04));
        /*change the flex alignment form the parent container*/
        align-items: flex-start;
        align-self: flex-start;
    }
</style>

It would be awesome to have "style hooks" for all components - this can be implemented through css variables/properties and would allow for things like dynamic theming including support for dark mode etc.

Because css variables/properties can be read and written through javascript this would open up several new ways for dynamic layouts.

CSS variable/properties are supported on all current browsers except IE 11, and it is possible to implement them with a gracefull fallback.

Currently, using npm install --save @progress/kendo-theme-material will get the standard Material Design theme for use across the React Components, but why is Material Black not available this way? (npm install --save @progress/kendo-theme-materialBlack)

Hi Team,

I'd like to request the ability to add a Body section within the ThemeBuilder where the user can set the Body of the entire web document.  The Body section of the ThemeBuilder appears to only affect the Chat UI.

Thank you!

We need a way to load/save themes.  The theme editor is honestly not very useful as it is.  This surely can't be hard to allow a user to upload a file and use that as the basis for making changes.  A one-off configuration is not how development works.  There was one ticket similar to this that was marked as fixed but bookmarking and loading from a page is a poor and easy way out way to do this imho.

A new Kendo UI theme which is in compliance with and extends Zurb Foundation styles -> http://foundation.zurb.com/sites/docs/kitchen-sink.html

The Themebuilder is way too narrow for me to style the product we are building properly. As a designer, I would like to be able to style most properties using a tool like that. E.g. I cannot style the grid except 3-4 properties. The example grid has no hierarchy, and most grid functions are not there for me to see/style. I have worked with your competition Infragistics before, and they have a very flexible AppStylist that allows me to change all style properties. 

I would like you to build something like that! And, of course, be able to import current CSS and not start from scratch every time...

When creating a custom build, it's highly impractical to trim down the theme css. The Less source breaks out common widget properties, but the primary themable file lumps all widgets together into a single massive file. It would be nice if this could be split apart further to trim out unused widget styles entirely.

Hello,

We want to create a custom Material theme for our ASP.NET Core web application. We are using the Sass Theme Builder but can only select predefined color swatches for the "Material" base theme. We would like to be able to set custom colors per "subject" just like you can with the "Default" and "Bootstrap" theme. 
Is this possible or are you blocking this on purpose for some reason?

Thank you in advance.

Currently there are 3 application themes: Default, Material, and Bootstrap.
These are nice and helpful however having 3 is quite a bit limiting.

I totally understand that a lot of people will and maybe should create a theme based on their own styles and preferences.
However I honestly think most people probably use a default theme and make small corrections to it in order to suit their needs.

-------

Admin edit: We will be keeping here a list of the suggestions, add your comment which one you would like to see implemented - if it's not on this list, we will add it:

• Dark (black) theme - you can find a basic sample attached below that uses #363636 for background and #d5d5d5 for text colors (two of the main colors for the Black Material theme we have in Kendo), you can further tweak things in the Theme Builder app
• Fluent UI - based on the Fluent UI by Microsoft
• Kendo Themes such as BlueOpal, Silver and Office 365 - you can generate them from the predefined color swatches on the left hand side of the Theme Builder app
• Theme that uses CSS, not SASS variables so that it can be customized at runtime - at the moment, you can generate the needed themes and switch them at runtime as shown here.

------

In WPF there are 20 or so styles.
Why only 3 in Blazor when the web is just as easy to style as WPF?

Please add theme based on CSS variables. That would allow developers to change theme at run-time and offer our customers similar experience that most (large) web sites offers, like Gmail, Office 365 online ...

Also, in the long run, this could be the only theme that's needed. All others could be based on this one.

Fluent UI is used in all major Microsoft 365 Apps. 

Why not make a Fluent UI theme for Blazor components? 

https://developer.microsoft.com/en-us/fluentui/#/controls/web

Especially with dark themes such as Metro Black, the traditional browser scrollbar does not really fit. I know scrollbar customization is not available in all browsers, but no fallback support is required (as the css is simply ignored by these browsers), and I believe it would greatly benefit users of the browsers that are supported.

Hi there,

as we are building apps for SharePoint and Office we are in need of a theme that looks like Office 365. Kendo UI for jQuery has that but there's a big shift towards building those apps with Typescript and React. Unfortunately the Kendo UI React package doesn't provide an Office 365 theme so everything we build doesn't integrate well to the look and feel of SharePoint and Office. 

It would be great if you were able to migrate that theme over from jQuery to the React components.

Thanks and kind regards

  Christian