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)

Telerik.Blazor.Components.TelerikSwitch`1[System.Boolean] requires a value for the 'ValueExpression' ValueExpression is provided automatically when using 'bind-Value'

On a grid grouped by one or more fields, provide an option for end users to expand/collapse all rows at will. The following image is a suggestion of where this option (most likely a button) should appear:

Looking for feature parity with - https://www.telerik.com/kendo-react-ui/components/grid/data-operations/odata-server-operations/

ADMIN NOTE: The goal is to expose a method like args.Request.ToODataString() for the grid OnRead event, so you can pass this on to a service so it knows the grid state (page size, current page, filtering,..). The grid will still expect the total of items and the current page of data to be set in the local fields.

Our grids / drop downs / comboboxes pull 1000s of items, resulting in JSON of 20mb+ if we pull all of the elements to the client.  The OData server operations have greatly reduced what we send over the wire, and have worked amazing well in our current React application.  Would love to have the same capability for Blazor client side.  We are treating Blazor as a client side replacement for React/Redux, we do not want to run Server Side Blazor.  

Hi.  Still in the trial phase, and I was curious about this.

I'm trying to develop two apps, one in ASP.NET Core and the other in Blazor WASM.

I found the ASP.NET Core Bottom Navigation which is perfect for the ASP.NET Core project.  Shown here.

However, I'd like to be able to show continuity as users transition to the Blazor project and I don't see a BottomNavigation component listed for Blazor.

Is this something that can be added to the Blazor UI tools, or is there an example someplace I can use to get started?

Thanks in advance.

Hi,

If Telerik can, at some point, develop a design tool like the Radzen Design Time, that would really be nice!

Thanks

In

            <FilterMenuTemplate Context="context">
                <TelerikCheckBoxListFilter Data="@NameOptions"
                                           Field="@(nameof(NameFilterOption.Name))"
                                           @bind-FilterDescriptor="@context.FilterDescriptor">
                </TelerikCheckBoxListFilter>
            </FilterMenuTemplate>

I would like to have a DisplayField or TextField so that i can show the user something meaningful, while still filtering based on IDs behind the scenes?

More details on the concept for custom data: https://docs.telerik.com/blazor-ui/components/grid/filter/checkboxlist#custom-data

All I ask is to give a way to have a proper working datepicker. Like your javascript datepickers. That doen't care only for right values but for the person that uses it. Telerik was an early adopter in the Blazor ecosystem, I don't know how they haven't yet fixed their datepickers.

You can do this with many ways. I don't know them all but I will propose some here.

1. Create a second datepicker component that works properly.
2. Put an attribute in the component to work with free-text
3. Maybe if this attribute is on you can switch behind between 2 different components
4. Find a other solution of your own.

In the end behind the scenes you shouldn't bind the datepicker input in the datetime property but to a sting one. DevExtress has done this right.

This will solve

1. Proper user expirience when a user uses the keyboard to edit dates
2. Copy-Paste issue
3. Clear date parts issue
4. all from 30/4/2022 to edit to 31/5/2022 with out having to clear the input
5. Strange editing of years (I have an example in the end)
6. Allow to have dots or what ever the users want between dates numbers. (e.x. 13.3.2022 )

I this is a trade-off and you will have senarios with wrong inputs and other things, but you already know them from the javascript world, and it's less importand than the aboves.

*Strange editing of years

Lets say that we have the year 1998 19and we want to put 2014.

the users See
-> 1/1/1998
-> 1/1/9982
-> 1/1/9820
-> 1/1/8201
-> 1/1/2014

That's not user friendly, and is very disturbing.

Hello there,

I encountered an issue with the TelerikForm component after upgrading Telerik.UI.for.Blazor from version 4.0.1 to 4.4.0. In the code below I have placed the two form items in a Bootstrap grid:

<TelerikForm Model="@person">
    <FormValidation>
        <DataAnnotationsValidator></DataAnnotationsValidator>
    </FormValidation>
    <FormItems>
        <div class="row">
            <div class="col-md-6">
                <FormItem Field="@nameof(Person.Id)" LabelText="Id"></FormItem>
            </div>
            <div class="col-md-6">
                <FormItem Field="@nameof(Person.FirstName)"
                        EditorType="@FormEditorType.TextArea"
                        LabelText="First name">
                </FormItem>
            </div>
        </div>
    </FormItems>
</TelerikForm>

With version 4.0.1, the two fields were displayed in two columns within the form element. However, with version 4.4.0, I noticed that the HTML code, specifically the div elements, are now rendered outside of the form element. The HTML structure looks like this:

<div class="row">
	<div class="col-md-6">
	</div>
	<div class="col-md-6">
	</div>
</div>
<form class="k-form telerik-blazor k-form-md" dir="ltr" style="">
	<div class="k-form-field">
		<label class="k-label k-form-label" for="a6cc8103-4d52-4377-8656-169e4a3de33a">
            Id
		</label>
		<div class="k-form-field-wrap">
......

I wanted to check with you if this change is intentional or if it might be a bug with the TelerikForm component in the latest version.

Best regards,

Ivaylo

This public feature request:

• Explains how the TelerikRootComponent works.
• Outlines the problems of the current software design in static .NET 8 Blazor apps.
• Measures customer demand for a major change that may possibly resolve the current limitations.

How the TelerikRootComponent Works

Historically, the TelerikRootComponent was designed with the following purposes:

• To host and render all Telerik Blazor popups as RenderFragments. This means that all popups are rendered where the TelerikRootComponent is defined in the application's component hierarchy. In most cases, correct popup position requires the TelerikRootComponent to wrap all the content on the web page. Otherwise the correct position is not guaranteed and this is documented. In addition, the TelerikRootComponent instance is a CascadingValue, which allows it to collect all popup RenderFragments.
• The TelerikRootComponent exposes parameters for global application-wide Telerik settings, such as icon type or RTL support. This is another reason why it makes sense to have a single TelerikRootComponent that wraps all the page content.

Problems and Limitations in .NET 8 Blazor Static Apps

.NET 8 Blazor apps with "Per Component" interactivity location create a big challenge for the above state of affairs:

• Cascading values do not pass across render mode boundaries. .NET 8 includes a new feature for passing cascading values to interactive components (builder.Services.AddCascadingValues()), but this mechanism does not support passing of RenderFragments, because they are not JSON serializable. This brings the requirement that the TelerikRootComponent is part of an interactive component hierarchy.
• When the TelerikRootComponent is in a non-layout .razor file, it triggers more re-renders than normally. They are related to internal MediaQuery instances and all popups, which the root component manages.

So, developers who work with a globally static app with specific interactive components ("islands of interactivity") may need to:

• Place the TelerikRootComponent somewhere inside the component hierarchy, so it can't wrap all the page content. This will lead to wrong popup position.
• Use multiple TelerikRootComponents. This requires to define the same parameters for each TelerikRootComponent instance.

Next Steps

All developers who develop static .NET 8 Blazor apps with "Per Component" interactivity location:

1. Please vote for this feature request, so that we can measure how many customers are affected by the described limitations.
2. Post here and describe:
   • Why do you need to use apps with "Per Component" interactivity.
   • Your specific challenges with the current TelerikRootComponent setup.

I'd like at least a linear gauge

*** Thread created by admin on customer behalf ***

I would really be happy to see your WPF Diagram Control (https://www.telerik.com/products/wpf/diagrams.aspx) ported to Blazor. 

Do you have any plans to do so?