The Pickers are not bound to model value when a nullable DateTime is set.
public class MyModel
{
public DateTime? Birthday { get; set; }
}
@(Html.Kendo().TimePickerFor(m => m.Birthday))
The Pickers are not bound to model value when nullable.
The Pickers are not bound to model value when a nullable DateTime is set.
Kendo UI version: 2024.4.1112
jQuery version: x.y
Browser: [all]
Dojo example.
The Chart's animation does not work when it is nested in the Splitter.
The Chart's animation should work.
.NET 6 introduced DateOnly and TimeOnly types, but none of the relevant date/time controls support these types.
There is already a feature request to support DateOnly in DatePicker; this feature request is about adding support for TimeOnly to TimePicker.
At this stage, the Serialize() method depends on Newtonsoft.Json:
using Newtonsoft.Json;
namespace Kendo.Mvc.Infrastructure
{
public class DefaultJavaScriptSerializer : IJavaScriptSerializer
{
public string Serialize(object value)
{
return JsonConvert.SerializeObject(value).Replace(@"<", @"\u003c").Replace(@">", @"\u003e");
}
}
}
Is it possible to remove the dependency and use the System.Text.Json serializer instead?
### Bug report
The attributes set through the "HtmlAttributes", "ContentHtmlAttributes", and "LinkHtmlAttributes"methods are not applied to the TreeView items.
### Reproduction of the problem
1. Create a TreeView and set attributes by using the "HtmlAttributes", "ContentHtmlAttributes", "LinkHtmlAttributes"methods:
@(Html.Kendo().TreeView()
.Name("treeview-kendo2")
.Items(treeview =>
{
treeview.Add().Text("My Documents")
.SpriteCssClasses("k-icon k-i-globe")
.Expanded(true)
.Url("/")
.HtmlAttributes(new { @class = "fairydust1" })
.ContentHtmlAttributes(new { data_navigate = "navigate_content", @class = "trigger", title = "content_title" })
.LinkHtmlAttributes(new { data_navigate = "navigate_link", @class = "trigger", title = "content_link" });
})
)
2. Run the page and inspect the TreeView item.
### Expected/desired behavior
The attributes are serialized and rendered.
### Environment
* **Kendo UI version: 2021.2.616
* **jQuery version: 1.12.4
* **Browser: [all]
### Bug report
When adding custom attributes to the CheckBox Taghelper, they are not added to the input element.
### Reproduction of the problem
1. Define a CheckBox Taghelper and add 'data-bind="checked: Test"' to its tag:
<kendo-checkbox name="Name" data-bind="checked: Test"></kendo-checkbox>
2. Inspect the CheckBox element and you will see that the "data-bind" attribute is missing.
3. When using the HtmlHelper version of the CheckBox, the attributes added through the HtmlAttributes() option are added as expected.
A REPL sample for reproduction: https://netcorerepl.telerik.com/mIuZlRle01kh6Ly043
### Expected/desired behavior
The specified attributes must be added to the input element of the CheckBox Taghelper.
### Environment
* **Telerik UI for ASP.NET Core version: 2024.2.514
* **Browser: [all]
When the clearSelection method of the ListBox is used for connected ListBoxes the toolbar buttons remain active.
The toolbar items of the ListBox remain active
The toolbar items of the ListBox must be disabled automatically
### Bug report
When using the @Html.EditorFor(m => m) configuration to initialize a MultiSelect TagHelper editor, and passing a specified value for its "id" attribute, the "name" attribute of the <select> element contains a prefix.
### Reproduction of the problem
1. Set the MultiSelect TagHelper as an editor editor of a specified Model property and set the "id" attribute using ViewData:
//Model
[UIHint("CustomMultiSelect")]
public IEnumerable<string> Names { get; set; }
//~.Views/Shared/EditorTemplates/CustomMultiSelect.cshtml
@model IEnumerable<string>
@{
var id = ViewData["id"]?.ToString();
}
<kendo-multiselect for="@Model" placeholder="some custom behavior" bind-to='ViewData["Data"] as List<string>' id='@id'></kendo-multiselect>
2. Define @Html.EditorFor(a=>a.Names, new{id="customId"}) in a form:
@model MyModel
<form id="myForm" data-method="POST" asp-action="Save" asp-controller="Home" class="k-form k-form-md">
<div class="k-form-layout k-d-grid">
<div class="k-form-field">
@Html.EditorFor(a=>a.Names, new{id="customId"})
</div>
</div>
...
</form>
3. When the MultiSelect is loaded, its "name" attribute is "Names.Names" rather than "Names":
When using the HtmlHelper version of the MultiSelect, the "name" attribute is correct:
//~.Views/Shared/EditorTemplates/CustomMultiSelect.cshtml
@model IEnumerable<string>
@{
var id = ViewData["id"]?.ToString();
}
@(Html.Kendo().MultiSelectFor(m => m)
.Placeholder("some custom behavior")
.BindTo((List<string>)ViewData["Data"])
.HtmlAttributes(new { id = @id })
)
### Expected/desired behavior
When using the @Html.EditorFor(m => m) configuration, the "name" attribute of the MultiSelect TagHelper must match the Model property name when the "id" attribute is set to a custom value.
### Environment
* **Telerik UI for ASP.NET Core version: 2024.3.806
* **Browser: [all]
Open this dojo example: https://dojo.telerik.com/BzNkZgSf
The input tooltip shows:
k-editor-link-url
because the input's title attribute is set like this: title="k-editor-link-url"
Instead of the name of a class, the tooltip should show "Web address", "Text", or "ToolTip" respectively.
The custom ordering of the filter values in the Telerik UI ASP.NET Core Grid does not function correctly when using TagHelpers.
A REPL sample for reproduction: https://netcorerepl.telerik.com/wIYNvEvn00CAqNGL14
The filter values should be presented in the same order as specified in the Filterable configuration.
### Bug report
The label configuration is not available for the plotband when using the TagHelper version of the Bar Chart.
### Reproduction of the problem
1. Open the following REPL sample: https://netcorerepl.telerik.com/woEMFDll17ui7F4122
2. The label of the plotband is not available.
3. The label option is available when defining the Chart by using HtmlHelpers: https://netcorerepl.telerik.com/QSYMvNFP187x0nAl24
### Expected/desired behavior
The plotband must have a label option.
### Environment
* **Telerik UI for ASP.NET Core version: 2024.3.806
* **Browser: [all]
Grid Hidden Column is set as exportable by default for Pdf and Excel
The Grid Hidden Column should be set as exportable by default for Pdf and Excel.
The Grid Hidden Column should not be set as exportable by default for Pdf and Excel.
The issue is reproducible when the TimePicker's dates configuration is set and its min() API method is called. Afterwards, if the user select a time, the component shows the wrong time (2h earlier) as selected.
The TimePicker shows a selected value that is 2h earlier than the actual time the user has selected.
The time the user selects is shown as selected value.
Toolbar.Items.Group.CustomTool() API of the Scheduler produces an invalid configuration.
To give more context, the Toolbar's buttonGroup items do not expose, nor should they expose a template
configuration. The currently available options advocate that each of the buttons must apply options similar to that of the ToggleButton.
Thus, making the wrapper configuration not applicable. The following dojo verifies this - https://dojo.telerik.com/@alexander64836/ayedUsAh
Toolbar.Custom.Items.Group.CustomTool() API configuration of the Scheduler produces an invalid configuration which is not serialized accordingly.
Toolbar.Items.Group API configuration of the Scheduler should expose a CustomTool() API configuration for the ButtonGroups.
The current workaround would be to declare the CustomTool via the Toolbar.Custom.Items.CustomTool() API configuration. And a ButtonGroup via the Template component:
@(Html.Kendo().Scheduler<Kendo.Mvc.Examples.Models.Scheduler.TaskViewModel>()
.Name("scheduler")
...
.Toolbar(t => t.Custom(c =>
c.Items(itm => {
itm.CustomTool(Html.Kendo().Template().AddComponent(c => c
.ButtonGroup()
.Name("select-period")
.Items(t =>
{
t.Add().Text(string.Empty).Icon("chevron-up");
t.Add().Text(string.Empty).Icon("chevron-down");
})
));
})
)
)
)
The following Telerik REPL illustrates this approach.
At this stage, the ToolBar.Custom() API configuration does not expose built-in configurations for adding a handler and partial view. E.g:
@(Html.Kendo().Grid <TelerikAspNetCoreApp455.Models.OrderViewModel>()
.Name("grid")
.ToolBar(toolbar => {
toolbar.Custom().Name("Test1").ClientTemplateHandler("someHandler");
toolbar.Custom().Name("Test2").ClientTemplateView(Html.Partial("_Test2"))
})
...
)
The ToolBar.Custom() API configuration does not expose built-in configurations for adding a handler and partial view.
The ToolBar.Custom() API configuration should expose built-in configurations for adding a handler and partial view.
Note: I already opened issue #7910 in the kendo-ui-core repo for this but wasn't sure if I should report this through the Feedback Portal.
The TextArea TagHelper does not render the "maxlength" attribute when set via data annotations.
Note: this is essentially the same issue from #6884 but applies to the TextArea helper (and not the TextBox helper), so perhaps the fix for that issue just needs to be applied to the TextArea helper (it's always that easy, right? 😉).
Given the following model property:
[StringLength(500)]
[DisplayName("Example")]
public string Example { get; set; }
The Kendo TextArea helper:
<kendo-textarea for="Example" rows="3"></kendo-textarea>
...generates code without the "maxlength" attribute:
<textarea
data-val="true"
data-val-length="The field Example must be a string with a maximum length of 500."
data-val-length-max="500"
id="Example"
name="Example"
data-role="textarea"
aria-disabled="false"
rows="3"
class="!k-overflow-auto !k-flex-none k-input-inner"
autocomplete="off">
</textarea>
The default ASP.NET Core TextArea helper:
<textarea asp-for="Example" rows="3"></textarea>
...generates code with the "maxlength" attribute:
<textarea
rows="3"
data-val="true"
data-val-length="The field Example must be a string with a maximum length of 500."
data-val-length-max="500"
id="Example"
maxlength="500"
name="Example">
</textarea>
The Kendo helper should generate the "maxlength" attribute like the built-in helper.
### Bug report
The ExpandAll() option does not expand or collapse the TreeView nodes.
### Reproduction of the problem
1. Enable or disable the ExpandAll() option.
2. The nodes are not expanded/collapsed when the TreeView is initialized.
A REPL sample for reproduction: https://netcorerepl.telerik.com/mSuMEPkZ10ZA6l8P00
### Expected/desired behavior
All nodes must be initially expanded when ExpandAll(true) is set.
### Environment
* **Telerik UI for ASP.NET Core version: 2024.2.514
* **Browser: [all]
At this stage, the Telerik UI for ASP.NET Core Notification allows setting arbitrary templates via the NotificationTemplateTagHelper. Despite the API documentation implying that the TagHelper can be nested, the following configuration:
<kendo-notification name="notifications" stacking="NotificationStackingSettings.Down" auto-hide-after="2500">
...
<templates>
<notification-template type="error">
<notification-template>
<p>Some Template</p>
</notification-template>
</notification-template>
</templates>
</kendo-notification>
It does not successfully serialize the Template TagHelper.
success
type is not serialized.The NotificationTemplateTagHelper does not serialize successfully the TemplateTagHelper.
The NotificationTemplateTagHelper should successfully serialize the TemplateTagHelper.