It seems like Blazor on the server-side will be re-branded as Razor Components. Will Telerik support it?
The CSS classes used by Blazor UI are not documented. (I haven't looked outside the Blazor area, so maybe it's somewhere else in the docs? My team has no need for other Telerik products.) On a similar note, the Themes page in the documentation explains how to reference alternate themes like Bootstrap, but it doesn't explain how to actually use the classes, or how it integrates with the real Bootstrap CSS, which have many various useful, well-known utilities like margin and padding settings, which don't seem to be part of the Telerik theme support. (I'm an architect at a very large corporation, we do have one of those includes-everything DevCraft licenses, I just can't log in with that account.)
For the Grid, is is possible to have a a SortField along with Field (that displays the data) in columns.
The SortField will be used instead of Field when sorting (if Grid is Sortable), like in WebForms: https://docs.microsoft.com/en-us/dotnet/api/system.web.ui.webcontrols.gridview.sortexpression?view=netframework-4.8.
Maybe you want to sort data based on other values instead of what is displayed.
This could be especially useful for dates that have been formatted for display in Field
but you don't want to use for sorting because date and string sorting is not the same.
Allow "items per page" and "1 - X of Y items" on the pager configurable or even allow them to be hidden/removed.
On mobile devices the telerik pager takes up too much room and needs to be more responsive. I'm already aware of this feature request: https://feedback.telerik.com/blazor/1442883-responsive-layout-for-the-pager
But I would like to take it a step further and be capable of customizing/removing the text.
Add the following Parameters to the TelerikPager:
[Parameter] public bool ShowItemsPerPageText { get; set; } = true;
[Parameter] public bool ShowXofYItemsText{ get; set; } = true;
<TelerikPager ShowItemsPerPageText="false" />
<TelerikPager ShowXofYItemsText="false" />
In my opinion this looks better
==============
ADMIN EDIT
==============
In the meantime, you can change the pager text through localization. It is important to keep the same number of placeholders, however, so that the string.Format() call it is used in will not throw.
This strings are behind the following keys:
It would be great if touch support could be added to the Blazor carousel component, to make it possible to swipe left and right on mobile devices. Presumably it would also drag left and right with a mouse on laptop/desktop machines.
At the moment the component isn't really usable on a modern website as it does not behave as users expect on mobile devices such as phones and tablets.
An example of this would be:
var orderParams = new DialogParameters();
orderParams.Add("SelectedOrderHeader", Item);
orderParams.Add("EditMode", "Add");
orderParams.Add("SelectedOrderDetail", new OMSOrderDetail());
DialogService.Show<OrdersDetailForm>("Click on orders grid to continue", orderParams);
<OrderDetailsForm> is a custom Blazor component.
Does the Telerik Blazor dev team have any plans for implementing something like this?
Since upgrading from 3.8 to 4.4 (including all new css) created dialogs from DialogFactory are sometimes behind an already opened modal window.
The reason for this seems to be an incorrectly, automatically calculated z-index of 10003 when the open dialog has 10006.
This does not always happen, there are scenarios where the first created dialog works fine, and the next called in the same method suddenly is behind the dialog, thus the error seems to be in telerik and not our side.
We could not yet find a proper workaround apart from creating custom dialogs.
I have an ENUM like this:
public enum DeliveryMailOptions
{
Regular,
[Display(Name ="FedEx Priority")]
FedExPriority,
[Display(Name ="FedEx Two-Day")]
FedExTwoDay
}
It is used in a data model like so:
[Display(Name = "Mail Option")]
public DeliveryMailOptions MailOption { get; set; }
When rendered, it ignores the Display attribute and only shows the enum text.
Can I use Translators or any other abstraction of Telerik component for my Selenium UI tests?
---
ADMIN EDIT
Even if Telerik does not provide some example translators to facilitate e2e testing with Selenium, you can build your own translators and abstractions to access the correct DOM elements. You can find some guidance in this forum thread: https://www.telerik.com/forums/xunit-selenium-tests.
---
The File Manager (exactly like https://www.telerik.com/aspnet-core-ui/file-manager) but for Blazor would be very nice.
There are no File Manager out there and this feature could support the purchase decision.
I would like to use scaffolding with Telerik UI for Blazor
**Admin Edit**
The plan is to be released in 3.3.0 release once extensions are thorougly tested.
**Admin Edit**
Hi Telerik,
I have been using MudBlazor for my latest project (smaller one), but we are scaling up for another larger project now and are looking at the Telerik UI for Blazor.
Does Telerik UI for Blazor have an equivalent to the MudBlazor AppBar, an application wide top bar which is persistent through out the application life cycle?
Its able to contain other controls ie drawer icon, login/out button, spacers etc.
PS: See attached screen dump of the app bar.
Best regards
Ulrik
The 300ms default transition time for popups is too long for our app, and I would like an option to set it globally. It looks great on demos, but turns the interface into a sludge for doing real work.
The original solution to https://feedback.telerik.com/blazor/1469662-way-to-modify-default-values-of-animations-such-as-duration-and-delay-for-a-component-such-as-combobox (from 2020) allowed a default animation speed through css.
However, with the new PopupSettings approach, animation speed is hard coded into the style attribute on the .k-popup, thwarting any attempts to override it globally. Adding PopupSettings to all components in our app is hardly a workable solution. The only workaround I've figured out so far is to disable animations on .k-popups alltogether (by adding a "transition: none" to .k-input)