Hi Alan,

Thank you for reaching back!

I understand your frustration and would like to apologise if we have set a wrong impression.

You have asked what is causing the delay on shipping a fix, so I will try to explain the reason behind it.

As you are probably aware the legacy node-sass compiler has reached end-of-life state and will no longer receive fixes even if they are related to security.

This also means that the @import syntax which we are currently using in our implementation will be completely removed.

With the above in mind we are currently working on upgrading to the latest dart-sass implementation and dropping support for node-sass, which requires significant infrastructure efforts and that is where our current focus lies.

This does not mean however that we will not be addressing important bug fixes like the one referred here.

I hope this provides some insight into what caused the delay and again aplogise for the inconvenience this has produced.

Regards,
Emil
Progress Telerik

Hello Alan,

First let me apologise for any inconveniece the reported behaviour has caused.

Please be informed that we have been made aware of this regression and have an official issue in our repository to which you can subscribe if you wish.

We will be prioritizing this regression and a fix should be available in one of the upcomming releases of the Kendo themes.

For the time being we can offer the following workaround through the disabled mixin:

@import'@progress/kendo-theme-classic/dist/all.scss';
// Overriding the dedicated disabled class
.k-disabled {
  @include disabled($opacity: .8);
}
// Or if you need to be more specific
.k-button.k-disabled {
  @include disabled( $bg: red, $color: white );
}
 

On the matter related to the compatibility with Kendo UI, the latest version of the package is compatible with v8.2.1 of the Kendo themes.

For more information or future reference you can visit this page.

Regards,
Emil
Progress Telerik