In Development
Last Updated: 29 Aug 2022 13:55 by ADMIN

Bug report

Incorrect id attribute is generated when the Value() configuration contains spaces. As a result a RadioButton component is not initialized.
This is a regression introduced with v2022.1.301

Reproduction of the problem

The following RadioButton definition:

@(Html.Kendo().RadioButton().Name("radioBtn1").Value("Value with spaces"))

generates an incorrect id attribute

<input id="radioBtn1_Value with spaces" name="radioBtn1" type="radio">
kendo.syncReady(function() {
    jQuery("#radioBtn1_Value with spaces").kendoRadioButton({
        "checked": false,
        "value": "Value with spaces"
    });
});

Expected/desired behavior

A valid id attribute should be generated.

TicketID:

1569749

Environment

  • Kendo UI version: 2022.2.510
  • Browser: [all]
In Development
Last Updated: 08 Jun 2021 08:45 by ADMIN
Created by: William
Comments: 3
Category: Grid
Type: Feature Request
16

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.