The ability to export a grid to excel has been a great addition, we would like the ability to export in CSV and XML also.
Add support for hidden fields. There could be an alternative way of adding them to the Items collection, e.g.
.AddHidden()
Consider the cases when the hidden field is bound to a model field and when it isn't bound to the model. The latter could be a scenario involving antiForgeryTokens:
<input type="hidden" name="__RequestVerificationToken" value="token" />In both cases you should be able to set the value of the hidden field programmatically and submit it with the form.
.Items(items =>
{
items.Add()
.Field(f => f.Type)
.Label(l => l.Text("Type:"))
.Editor(e =>
{
e.Upload()
}
}
I'm currently evaluating the ASP .Net Core Components and whilst I'm liking it so far, I have to say - the documentation leaves a lot to be desired.
At the moment, I am trying to use grid and looking at documentation, I have no idea if I am meant to be looking in Kendo.Mvc.UI.Fluent or Kendo.Mvc.UI - and when I am there and find an item, there just isn't enough detail. In addition, the demos section appears to actually be more helpful and I'm constantly looking there.
What caused me to write this is that I have simply enabled GridFilterMode.Row on an instance and whilst I like it, I want to change the default from "Is Equal To" to "Contains"... I have been experimenting for the past few hours without any luck and I'm going round in circles on documentation:
I can see that Filterable requires GridFilterMode, but the documentation is lacking - https://docs.telerik.com/aspnet-core/api/Kendo.Mvc.UI/GridFilterMode#kendomvcuigridfiltermode
I then try to find the filterable modes documentation, but, half the features/methods just don't seem to have any affect whatsoever.
Personally, I'm having great luck learning about your components from the demo section and adapting the code to suite my needs - but, if there isn't a demo, it appears to be a very hard task to learn what is and isn't possible.
I'd like DateOnly support to be introduced to Telerik UI for ASP.NET Core because my Grid uses that type and issues occur in the Grid's PopUp and InLine editing fields that are bound to DateOnly fields.
Implement Recurrence Rule Parser helper that uses the Scheduler recurrenceRule string and parses it in a usable format on the server.
There is already a similar helper for Telerik UI for ASP.NET Ajax.
Per the documentation for the Grid's Search Panel:
"When the server operations are enabled, you can search only by using string fields."
This is an oddly-specific limitation to have that causes an awkward user experience. Grids in some areas with limited data might use client operations and, as a result, the Search Panel is capable of searching all columns in a Grid. Other areas, however, might have grids with significantly more data and be using server operations for performance reasons. A side-effect of this would mean the Search Panel is incapable of filtering on non-string fields. This not only might lead to unexpected results to an end-user, but also requires the developer to explicitly list each string field that can be searched. If a developer forgets to list only string fields, the default action will be for it to attempt to filter on all fields. If any fields happen to not be strings, you still get a loading indicator as if it's attempting to filter, but the Ajax request silently fails and returns an error 500 behind the scenes.
There are some manual workarounds discussed here, as well as some information as to why this limitation exists. It seems like the problems causing these limitations are known, as are some rough workarounds to get around it. It would be great if we could get some official support to address this limitation so developers aren't left to either work around it on their own or avoid using this feature altogether. This feature would be great if it weren't for this limitation. A single place to quickly and easily type in something to filter on, and have that filter applied against all columns could definitely save some time and be very useful, but with this limitation with a pretty technical explanation (from an end-user perspective), the unexpected mixed results could instead lead to confusion and frustration, and distrust of this feature.
Due to changes in the ASP.NET Core framework and how the Authentication is implemented the MVC5 implementation of the SecurityTrimming option became obsolete.
1. Allow the elastic behavior of the PDFViewer's mobile scroller to be disabled. Currently, when scrolling to the top or to the bottom, the document jumps and then immediately re-adjusts its position under the widget's header/bottom border.
2. Add the ability to manually scroll the document up/down with mousedown.
3. Add keyboard scrolling support.
Having a floating label functionality similar to the one available for the native Vue DropDownList, would be nice to have.
Bug report
The DataSource's property groupPaging: true prevents the Grid's group from expanding if it has a defined groupHeaderColumnTemplate.
Reproduction of the problem
- Open this Dojo
- Try to expand the Grid's groups
Also reproducible in the Core wrapper where an error is thrown: kendo.all.js:8743 Uncaught TypeError: Cannot read property 'hasSubgroups' of undefined
Current behavior
groupPaging is not compatible with the groupHeaderColumnTemplate
Expected/desired behavior
groupPaging and the groupHeaderColumnTemplate should be compatible
Environment
-
Kendo UI version: 2021.2.616
-
Browser: [all]
Bug report
When a Telerik UI Window is draggable and has its Position set, the first time the widget can be dragged, or it is being dispositioned while dragging.
Reproduction of the problem
1. Create a Telerik Window widget.
2. Set the Position.Left and Position.Top
3. Open and drag the window.
Expected/desired behavior
The window should be smoothly draggable.
Environment
* **Kendo UI version:** 2021.2.511
* **jQuery version:** 1.12.4
* **Browser:** [all]
IgnoreCase property is missing for the filterable options of the column:
The option is documented in:
Currently, the functionality for creating a toolbar template with TagHelpers is not available.
We have the need to create a chart to display Risk Information. Below is the image of a risk matrix as defined on pages 96 in AFPAM63-128 https://static.e-publishing.af.mil/production/1/saf_aq/publication/afpam63-128/afpam63-128.pdf -- there are more examples on page 101
Another example of a risk matrix can be seen on page 18 here -> https://static.e-publishing.af.mil/production/1/af_se/publication/afi90-802/afi90-802.pdf
I've copied the images here for convenience.
Would it be possible to add this to the Kendo Chart backlog?
If there is a text binding to the item that has a script tag injected, the Core component will break its initialization instead of encoding it as it is done for the Telerik UI for ASP.NET MVC DropDownList helper.
@(Html.Kendo().DropDownList()
.Name("DDL")
.HtmlAttributes(new { style = "width:100%" })
.OptionLabel("Select...")
.DataTextField("text")
.DataValueField("value")
.Height(310)
.BindTo(new List<object> {
new { text = "Test", value = 0 },
new { text = "<script>alert(123)</script>", value = 0 }
})
)Result:
Bug report
TextArea wrapper does not render correctly in v2021.1.224
Reproduction of the problem
Declare a Html.Kendo().TextArea() in ASP.NET project
Current behavior
The TextArea value does not retain.
Expected/desired behavior
TexArea shall render as in previous Kendo Ui versions
Related to Ticket #1509117
Environment
Kendo UI version: 2021.1.224
Browser: [all]
Bug report
The Kendo UI Grid's pager for UI for ASP.NET Core does not have an "All" option and it can't be configured in the Razor syntax.
Current behavior
Using the Kendo UI Grid's pageable.PageSizes, the ALL option is not available for UI for ASP.NET Core as it's only an Int32[].
Expected/desired behavior
The All option should be included like in the UI for ASP.NET MVC Razor Syntax.
Environment
- Kendo UI version: 2020.3.915
- Browser: all