The 1.1.0 release of Telerik UI for Blazor is here, providing many quality of life features and bug fixes to existing components.
The development team behind Telerik UI for Blazor is not one to sit back and relax - which is why I can announce that today we have the 1.1.0 release not even two weeks after the initial launch of 1.0.0!
This release brings some new features to existing components, as well as some bug fixes that are worth highlighting, so let’s dive right in.
Blazor Button Component
The Button component now exposes a
type attribute that allows you to define different types of buttons based on your desired behavior - just like the
type attribute on a regular HTML button element.
By default the Telerik UI for Blazor Button renders a
<button type="submit"> element, but if you want to mix things, up as of today, we have the following options available on the
ButtonType property of the component:
Submit - Renders a
type="submit" attribute. Can submit the form and trigger validation. This is the default value.
Button - Renders a
type="button" attribute. Does not invoke form validation and submission.
Reset - Renders a
type="reset" attribute. Can reset the current form.
Blazor DateInput Component
invalid states of the DateInput are now triggered correctly.
Blazor DropDownList Component
ValueField property now has a
Guid property, which means that the
ValueField properties can now be one of hte following types:
number (such as
double and so on)
We also took care of some issues we had around validation with the DropDownList.
Blazor Grid Component
With this release we took care of a couple of quality of life items for the Telerik UI for Blazor data grid. Namely:
- The Grid’s height can now be set to 100%
- Grid Command buttons no longer trigger form submission and validation. This improves the in-line editing experience quite a lot!
- Grid events are now asynchronous
- We added built-in validation to Grid Popup editor
Some of the bigger bug fixes we took care of for this release are:
- Resolved an issue where the Grid Popup editor could appear off-screen on a vertically scrolling page
- Grid filtering will now reset to the first page to ensure all results are properly seen (if there are any results)
- Fixed an item where a nullable boolean property could not be edited in the Grid
- Resolved the issue where a non-editable cell (read only) could be edited with inline edit mode
Blazor TabStrip Component
You can now access the
Title property of the current active tab. So, if you have a Tab Strip defined like:
<TelerikTabStrip ref="@myTabStrip">...</TelerikTabStrip> you could access the Title of the current selected tab using
Interested in Blazor?
Is this the first time you’ve heard of Blazor or Telerik UI for Blazor? Well, if that’s the case then I recommend heading over to the Telerik UI for Blazor overview page to find out more! You’ll find some more information about the Blazor framework itself, as well as sing up for a trial of our UI components - all from one convenient place!
Want to Influence What’s Next?
We continue to improve and add to our list of UI components for Blazor and it’s all based off of your feedback! If there are components you wish that we would work on, or features that you want to see in existing components, feel free to comment in the section below or head over to our public feedback portal for Telerik UI for Blazor to make your voice heard!