[Solved] Release Notes leave much to be desired, 14.0 ...

[Rob]

Telerik release notes are pretty generic with little or no detail references especially to "breaking changes".

Release History

For example:

No links to an example of code with "Before" and "After" needed to adjust for the Breaking Changes. 

So what is "smartbox mode" ... no link to what this feature is and how it would be used.

On "New" features there is no link/reference to where these "New" feature was requested nor number of requests.  Some sort of direct link showing who wanted the feature and why.

And we're still missing a lot of basic features like a Print option for Scheduler that will format/size the Schedule automatically to the output ... we're still using JS work-arounds.

Still no documentation on various CSS for on controls so we can quickly identify and adjust as needed ... avoid having to do painful browser developer mode hunting for what we need and setting pause of control states to discover etc.

Still no easy adjustments to visuals of DialogFactory.

Still issues with leaving a grid cell and clicking on a button outside the grid and losing data entered because the user didn't hit the Enter key.

I know I've said this before, but it's disappointing and does make one wonder if Telerik think Blazor is going to have a short life cycle hence isn't getting much development attention.  I get that Microsoft have burned us all in the past (Silverlight for example) but MS do seem committed to Blazor this time around as they continue to add more and more .NET support for it and it will replace ASPX.

Telerik support is top notch (you folks excel here), but there seems to be lack of product direction and frankly feedback process seems entirely useless.

Rob.

[Brian]

Agreed, and I would add the change pain for v14 was unusually bad. We are using several of the SvgIcons you chose to remove, and the styling/color changes were unpleasant as well ( we were using the removed Secondary and Tertiary AppBars for example ).  I realize you've got SvgIcons and Fonts and the Kendo styling system underlying all your products, and so they're not technically a part of Blazor UI. But you should still indicate those breaking changes at the top of the change notes page where you list all the various support library versions that were updated to version ###.  For example, a * Breaking * marker with a link to that product's change notes would help.

Thanks, Brian

[Rob]

Agree Brian ... and they just seem to be arbitrary.  No idea how Telerik think what they listed for V14 actually qualifies as a major version change?  

Telerik have a lot of competition from; SyncFusion, Infragistics, DevExpress, and more.  Telerik support is currently the only reason we're sticking with Telerik but as our work piles up and users demand more it's becoming increasingly difficult to stick with Telerik UI Blazor.

[Dimo]

Hello Rob, Brian,

Thanks for your feedback. I agree that more details and links in the release notes will be beneficial for everyone and we are considering this as an enhancement.

Currently, please use the release notes together with our Upgrade documentation:

• Breaking (API) Changes
• Rendering (HTML) Changes

>> No links to an example of code with "Before" and "After" needed to adjust for the Breaking Changes. 

I just added Breaking Changes in the Chart in version 14.0.0. The deprecated Chart template syntax was removed from our documentation three years ago to discourage developers from using it.

>> So what is "smartbox mode" ... no link to what this feature is and how it would be used.

See Grid Smart Box

>> On "New" features there is no link/reference to where these "New" feature was requested nor number of requests.

What benefit will such information bring to you? We can link to the related feedback portal item (if such exists), but that will not provide information about the new API.

>> does make one wonder if Telerik think Blazor is going to have a short life cycle hence isn't getting much development attention

We have discussed this before and you know we are committed to Blazor. Every major release of ours introduces new components, including complex ones that took a lot of effort to develop (e.g. the TaskBoard in our latest release).

>> Print Scheduler

The customer demand for this is low, hence we are focused on other tasks.

>> Still no documentation on various CSS for on controls so we can quickly identify and adjust as needed ... avoid having to do painful browser developer mode hunting for what we need and setting pause of control states to discover etc.

We have discussed this before too and I still believe that the browser's DOM inspector is the fastest and most effective way to override theme styles. You can regard it as the API reference for CSS.

>> Still no easy adjustments to visuals of DialogFactory.

This task was recently moved to our short-term backlog. You can follow Support MarkupString for the DialogFactory for official updates.

>> Still issues with leaving a grid cell and clicking on a button outside the grid and losing data entered because the user didn't hit the Enter key.

I assume that you are referring to your private ticket 1700598 from November 2025. There are two conclusions from it:

• A custom Save button should be disabled while the Grid is in active in-cell edit mode. The built-in in-cell editing does not have a Save button and using buttons while in active edit mode may cause race conditions in the event sequence. I am not sure there is a good or reliable way to avoid this.
• A public bug report related to text selection during in-cell editing.

>> we were using the removed Secondary and Tertiary AppBars for example

It turned out that these two theme colors were removed by mistake and our next release will include them back. Sorry about that. As a temporary workaround, you can use the underlying CSS classes:

<TelerikAppBar ThemeColor="@ThemeConstants.AppBar.ThemeColor.Primary">
    <AppBarSection>
        Primary AppBar
    </AppBarSection>
</TelerikAppBar>

<TelerikAppBar Class="k-appbar-secondary">
    <AppBarSection>
        Secondary AppBar
    </AppBarSection>
</TelerikAppBar>

<TelerikAppBar Class="k-appbar-tertiary">
    <AppBarSection>
        Tertiary AppBar
    </AppBarSection>
</TelerikAppBar>

>> I realize you've got SvgIcons and Fonts and the Kendo styling system underlying all your products ... But you should still indicate those breaking changes at the top of the change notes page ...

Telerik UI for Blazor depends on icon package versions 4.x, which do not remove icons. Some icons are marked as deprecated and are removed in the next version 5.0.0. Perhaps you have referenced the version 5.0.0 explicitly? We will document the breaking changes when Telerik UI for Blazor starts depending on icons v5.

Regards,
Dimo
Progress Telerik