The Kendo UI for jQuery Scheduler exposes toolbar.items.mobile option that allows you to define the desired tools in in adaptive rendering mode. Is it possible to implement the same option for the Scheduler Html and Tag Helper?
for
attribute to support model binding, similar to the HTML Helpers CheckBoxFor(m=>m.MyBoolProperty)
.
Model binding is supported for the TextArea HTML Helper
@Html.Kendo().TextAreaFor(x => x.Test).Rows(3)
but the corresponding option for the TagHelper is not implemented
<kendo-textarea for="@Model.Test" rows="3"></kendo-textarea>
At moment the "ForeignKey" method supports only predicates. Is it possible to implement a String overload (a screenshot is attached)?
Currently, to set a field's label and text the Wizard's Label() and Title() options must be used:
items
.Add()
.Field(p => p.DropdownId)
.Label(l => l.Text("Dropdown"))
.Title("Dropdown")
It would be helpful if the Wizard can be configured to get these from the data annotation attributes in the model:
[Display(Name = "Dropdown")]
public int DropdownId{ get; set; }
Hi.
In Kendo UI for ASP.NET MVC, I'm able to import the following file types into the Editor:
Docx
Rtf
Html
Plain Text
I'm also able to export to the following file types:
Docx
Rtf
Html
Plain Text
I expected this functionality to also exist in the Editor control in Kendo UI for ASP.NET Core.
This functionality seems to be missing from Kendo UI for ASP.NET Core.
Related post: https://www.telerik.com/forums/export-to-rtf-or-docx
Thank you.
Hello,
under
https://demos.telerik.com/aspnet-core/checkbox/index
I found that a checkbox can be used as a telerik component.
Unfortunately my intellisense does not show a suggestion for checkbox when I try to use it as a tag helper.
So my question ist:
Can checkbox be used with Tag Helper in Asp.Core 3.1 (Razor Pages) ?
Regards
Since support for cancellation token on user vote:
was declined and is unplanned.
I would like to implement it by myself.
However most of methods used by code is private or internal, so extending current one is difficult to achieve without copying a lot of existing methods and marking them public. It would be good make them part of public api so implementing own extension to ToDataSourceResult and ToTreeDataSourceResult would be possible. Currently it is not.
Kind Regards
Marcin
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.
Having a floating label functionality similar to the one available for the native Vue DropDownList, would be nice to have.
https://www.telerik.com/kendo-vue-ui/components/dropdowns/floating-labels/
Provide built-in integration of RadioButton / RadioGroup in the Form
i.e. : .Editor(e =>The built-in upload components event cannot be handled through the TagHelper:
<kendo-filemanager name="filemanager">
<upload on-upload="onUpload"></upload>
...
</kendo-filemanager>
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.