Could you consider implementing a component for adding a "contextmenu" to any kind of markup/components. This is very important for more packed UIs and business applications.

A text/ html editor similar to asp.net core

 

https://www.telerik.com/aspnet-core-ui/editor

I would like a simple list with templates for my items. Much like the grid, but not confined to cells and rows.

All controls (such as TelerikGrid, TelerikDropDownList, etc) should have a "Visible" property. This bindeable boolean value controls whether the control is visible on the page or not:

<TelerikGrid Visible="@IsVisible" />

@functions {

protected bool IsVisible

}

This is a much better method than surrounding the entire control's markup in an @if(IsVisible) block, since that causes the control to get removed/added to the dom at runtime. This can cause many issues such as the control's constructors being fired multiple times, the dom getting "jiggled" about unecessarily.

I feel the "Visible" property is a cleaner way to hide controls.

A basic Menu control is one of the most fundamental common controls ....  Why was it not included in the first release of UI for Blazor???

How about a basic fundamental Menu control in the UI for Blazor?   If not now, when?

At the moment, dropdown and popups (like the DatePicker and DropDownList) render in the place of declaration, and CSS rules from their parent elements affect them heavily (for example, they are hidden behind grid cells when used as custom editors).

The popups should be detached and rendered higher in the DOM if possible, so they don't get confined in their parent like that. This may be applicable for more components as well.

Would be great to have a user XML Editor, with input/output from string/stream and an attached XSD for continuous validation?

I realise this wouldn't be priority, just wondered if it could be put on roadmap at some point.

Many thanks,

David Speak. 

When following the Blazor UI code examples for the Grid, the source for index.cshtml contains the following:

@page "/grid/index"

@using Telerik.Blazor.Components.Grid
@using TelerikBlazor.Shared
@inject HttpClient Http

Notice that the using directive for the Shared component doesn't have a . separating Telerik and Blazor. It should read:

 

@using Telerik.Blazor.Shared

For example we have built a web application using ReactJS which uses video and phone API capabilities from Twilio. If there are built in blazor components, application development becomes easy. 

Ability to edit and save HTML content

Many applications need to play video content

Many applications need an ability to schedule people/resource.

Most of the screens need to provide visual feedback to users when some work is in progress. We are using MVVM, this should play nice with MVVM pattern.

This is a request for a new feature that I haven't seen across all of the Telerik products.

A new control that makes use of the HTML Canvas to allow for inking within web applications.

Can be used for free hand writing (inking) on mobile devices instead of requiring online keyboard in limited real estate scenarios. Can use to implement signature blocks on forms, convert to text, etc.

 

A DateTime picker that 'understands' localized standard/daylight savings time and prevents entry of an illegal time in the spring 'leap forward' and disambiguates the st/dt with the same hour during the 'fall back' is desired. It is almost impossible to get a good UX if there are separate Date & Time pickers meant to populate a single DateTime value.

Hello Team;
Hope you're enjoying your well-deserved holiday.

As the new features arrive, the new/update docs will be arriving too. In order for us to stay on the top of all the changes taking place on the Doc section, I'd like to suggest to have a page that each line contains:
a) Date
b) Doc description
c) A link to that section

This way, we can regularly look at this list and jump to the new docs to stay up to date with the team.

Thanks!
..Ben

Hello Team;

The current Blazor demo, runs as a client that is being hosted by a server side project. In the client project under wwwroot folder, there is an index.html there that acts as Blazor loader, with a fancy CSS animation and etc.

My suggestion for the RTM version of Telerik Blazor is to have something similar to this index page the we can use in out application that we can customize it a bit more.

I see a series of script files and links that many not needed for our apps.
It's just a thought and hope it can be done.

Thanks!
..Ben

https://www.telerik.com/kendo-react-ui/components/tooltip/

Tooltip is another one of those controls we use everywhere, would like to see a Blazor implementation. 

Looking for the TreeList control from kendo-ui to be brought over from jQuery to Blazor https://www.telerik.com/kendo-ui/treelist

 

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.