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.
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)
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:
In WPF there are 20 or so styles.
Why only 3 in Blazor when the web is just as easy to style as WPF?
Fluent UI is used in all major Microsoft 365 Apps.
Why not make a Fluent UI theme for Blazor components?
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.
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
Kendo provides a means to build your theme with SCSS variables in the build process. It would be great if it were possible to have these variables scoped to specific contexts, eg <div class="panel-dark"> receives the panel-dark themes, whereas if it is a child of "panel-light" then it receives the panel-light themes. Some of these kinds of features may be on the way with upcoming Custom Element features eg :part, :theme, but could potentially be possible today by having a style transclusion component, something like <kendo-theme-adjuster [styleCallback]="scssVariableSetter()"><my-content></my-content></kendo-theme-adjuster>. We need to support a variety of component themes simultaneously (not just switch back and forth) within a single app, and would like to not need to manually override all the kendo styles in these situations.
All the themes has Mobile support except the kendo.bootstrap-v4, we need the mobile support for new bootstrap v4. current bootstrap 4 css : https://kendo.cdn.telerik.com/2017.3.1026/styles/kendo.bootstrap-v4.min.css Expected Mobile Support css : https://kendo.cdn.telerik.com/2017.3.1026/styles/kendo.bootstrap-v4.mobile.min.css
For now 2 css are used (kendo.common.css and kendo.theme_name.css) for whatever widgets are present on the page. Would be nice to have styles for different widgets separated into single css files (as it is in jQueryUI), so that, if I need only a DropDownList on the page, I include something line "kendo.core.css" and "kendo.dropdown.css" and the whole css framework would not be downloaded each time.
In the new SASS Default v2 theme, you took away too much contrast compared to the original default theme. Why? Don't you know that many people find it hard to read things where the text color is too close in value to the color of the background color?? Please stop with the very low contrast.