Completed
Last Updated: 20 Feb 2024 11:50 by ADMIN
Release 2024 Q2

Bug report

The form is not serialized correctly when declared in the Template component

Reproduction of the problem

  1. Open the following Telerik REPL.
  2. Notice that the Form component declared in the Template is not serializing its options correctly.

Current behavior

The Form is not serialized correctly when declared in the Template component.

Expected/desired behavior

The Form should be serialized correctly when declared in the Template component.

Environment

  • Kendo UI version: 2024.1.130
  • Browser: [all]
Completed
Last Updated: 07 Nov 2023 08:46 by ADMIN
Created by: Charles
Comments: 0
Category: Form
Type: Bug Report
1

Bug report

Using a UI for ASP.NET MVC/Core Form, if a boolean property is defined as required with the [Required] attribute, and the Hint() option is not defined, the Form does not validate the checkbox.

Reproduction of the problem

Please visit the following Live demo, and submit the form.

Current behavior

The form will submit without validating the checkbox.

Expected/desired behavior

The Required attribute should be evaluated for validation.

Environment

  • Kendo UI version: 2023.2.606
  • jQuery version: All Supported Versions
  • Browser: all
Completed
Last Updated: 16 Oct 2023 05:52 by ADMIN
Created by: Steven
Comments: 0
Category: Form
Type: Bug Report
0

Bug report

Form TagHelper does not expose a ValidationSummary tag.

Current behavior

The Form TagHelper's exposes only a validation-summary attribute instead of a validation-summary tag which prevents adding options such as: Container, Enable, Template, and more.

In comparison to the HTML Helper .ValidationSummary() API configuration which allows the following:

        .Validatable(v =>
        {
            v.ValidationSummary(validationSummary => {
                validationSummary.Enable(true);
                validationSummary.TemplateId("someTemplate");
                validationSummary.Container("myContainer");
            });
        })

Expected/desired behavior

It would be a good idea to consider altering the current validation-summary attribute into a standalone tag helper. However, this will inevitably lead to a breaking change.

Environment

  • Kendo UI version: 2023.2.829
  • jQuery version: x.y
  • Browser: [all]
Unplanned
Last Updated: 17 May 2023 17:02 by Chiel
Created by: Chiel
Comments: 0
Category: Form
Type: Feature Request
1
Expose the ability to add a built-in password editor for the Form.
Unplanned
Last Updated: 16 Mar 2023 05:47 by Chiel
Add a configuration option for setting all labels as floating labels.
Duplicated
Last Updated: 13 Mar 2023 14:32 by ADMIN
Currently, the Display[Name = '"..."] could not be used to render the text of the labels in the Form. Please add support, so the DataAnnotations to be used in the Form labels. 
Completed
Last Updated: 25 Oct 2022 06:32 by ADMIN
Release R1.2023-Increment.1(09.Nov.2022)

Bug report

When a Telerik UI for ASP.NET Core MultiSelect is used in a Form, a JS error is thrown:

jquery.min.js:2 Uncaught Error: Syntax error, unrecognized expression: #
    at Function.se.error (jquery.min.js:2)
    at se.tokenize (jquery.min.js:2)
    at se.select (jquery.min.js:2)
    at Function.se [as find] (jquery.min.js:2)
    at S.fn.init.find (jquery.min.js:2)
    at new S.fn.init (jquery.min.js:2)
    at S (jquery.min.js:2)
    at Object.data ((index):24)
    at init.setup (kendo.all.js:6596)
    at init.read (kendo.all.js:6574)

The issue occurs when using jQuery 3.6.0, but is absent with jQuery v 1.12.4

Reproduction of the problem

@(Html.Kendo().Form<FormViewModel>()
        .Name("exampleForm")
        .HtmlAttributes(new { action = "Items", method = "POST" })
        .Validatable(v =>
        {
            v.ValidateOnBlur(true);
            v.ValidationSummary(vs => vs.Enable(true));
        })
        .Items(items =>
        {
               items.Add()
                        .Field(f => f.MultiSelect)
                        .Label(l => l.Text("MultiSelect:"))
                        .Editor(e =>
                        {
                            e.MultiSelect()
                                .HtmlAttributes(new { })
                                .Placeholder("Select...")
                                .DataTextField("ProductName")
                                .DataValueField("ProductID")
                                .HtmlAttributes(new { style = "width:100%" })
                                .Height(520)
                                .DataSource(source =>
                                {
                                    source.Read(read =>
                                    {
                                        read.Action("Items_GetProducts", "Form");
                                    })
                                    .ServerFiltering(true);
                                });
                        });
             })
    )
    public class FormViewModel
    {
        public List<ProductViewModel> MultiSelect { get; set; }
    }

Runnable sample available in ticket 1540812

Expected/desired behavior

JavaScript error should not be thrown.

Environment

  • Kendo UI version: 2021.3.914
  • jQuery version: 3.6.0
  • Browser: [all]
Completed
Last Updated: 24 Oct 2022 12:05 by ADMIN
Release R1.2023-Increment.1(09.Nov.2022)
Currently, the Telerik ASP.NET Core Form component does not display the name of the property that is set through the "DisplayAttribute.Name Property". Is it possible to implement it?
Completed
Last Updated: 13 Oct 2022 07:40 by ADMIN
Release R1.2023-Increment.1(09.Nov.2022)
Created by: René Spruit
Comments: 0
Category: Form
Type: Bug Report
0

Bug report

The Form TagHelper does not provide support for hidden fields, similar to the HtmlHelper.

Reproduction of the problem

The Form TagHelper does not allow similar built-in configuration:

.Items(i =>
            {
            i.Add()
                .Field(f => f.UserID)
                .Editor(editor => editor.Hidden());
            })

Expected/desired behavior

The Form TagHelper should support hidden inputs.

Workaround

Similar result can be achieved by setting the editor-handler attribute, creating a hidden input and setting an empty label:

<form-items>
    <form-item field="UserID" editor-handler="hiddenEditor" >
        <item-label text=" " />
    </form-item>
</form-items>

<script>
    function hiddenEditor(container, options) {
        $('<input type="hidden" data-bind="value: ' + options.field + '" name="' + options.field + '"/>')
            .appendTo(container);
    }
</script>

Environment

  • Kendo UI version: 2022.3.913
  • Browser: [all]
Completed
Last Updated: 08 Jul 2022 05:52 by ADMIN
Release 2022.R2.SP.next

### Bug report

When the DropDownTree control is added as a Form editor through the Editor() method, there is an ArgumentNullException "Value cannot be null. (Parameter 'key')".

### Reproduction of the problem

Attached is a demo that replicates the issue.

If the DropDownTree is defined outside of the Form, it is bound to the Model property as expected.

### Expected/desired behavior

The DropDownTree editor should bind to the Model property in the Form.

### Environment

* **Kendo UI version: 2022.1.412
* **jQuery version: 1.12.4
* **Browser:** [all]

Unplanned
Last Updated: 02 Jun 2022 17:07 by Jon
Created by: Stefania
Comments: 1
Category: Form
Type: Feature Request
23
Allow configuring the Upload component through the .Items configuration:
.Items(items =>
{    
    items.Add()
        .Field(f => f.Type)
        .Label(l => l.Text("Type:"))
        .Editor(e =>
        {
            e.Upload() 
        }
}

Unplanned
Last Updated: 07 Mar 2022 08:29 by n/a
Created by: n/a
Comments: 0
Category: Form
Type: Feature Request
3

At moment the Form Group does not support the HtmlAttributes() method. Is it possible to implement?

For example:

@(Html.Kendo().Form<Model>()
  .Name("exampleForm")
  ...
  .Items(items =>
  {
    items.AddGroup()
      .HtmlAttributes(...)
      .Items(i => {...});
  })
)

Completed
Last Updated: 07 Sep 2021 06:17 by ADMIN
Release 2021.R3
Created by: Bas
Comments: 3
Category: Form
Type: Feature Request
48

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.

Unplanned
Last Updated: 13 Aug 2021 06:40 by ADMIN
Created by: Muttley
Comments: 0
Category: Form
Type: Feature Request
0

The Kendo Form should include native ListBox editor support including joining and swapping items between two ListBox's using ConnectWith.

To use a ListBox in the Kendo Form currently requires a custom editor which is overly complex.

Completed
Last Updated: 28 Apr 2021 07:36 by ADMIN

Bug report

RadioGroup Validation fails always when Component is bound to Model

Reproduction of the problem

  1. Define a FormViewModel and set its data annotation to [Required]
  2. Initialize a Form and pass it the FormViewModel
  3. In the Form:
  • set up Validation
  • define an Item that uses the RadioGroup Editor
  1. Run the application choose a RadioGroup option and submit the Form

Current behavior

All the inputs of the RadioGroup Component get the data-val-required property and validation always fails

Expected/desired behavior

The RadioGroup's Validation should succeed, if one of the options is selected

Environment

  • Kendo UI version: 2021.1.330
  • Browser: [all ]
Completed
Last Updated: 16 Mar 2021 07:43 by ADMIN
Created by: Edwin
Comments: 1
Category: Form
Type: Feature Request
3

Provide built-in integration of RadioButton / RadioGroup in the Form

i.e. :     .Editor(e =>
                    {
                        e.RadioButton();
                    });
            });
Completed
Last Updated: 08 Jun 2020 12:15 by ADMIN
Release 2020.R2.SP.next

Form with MultiSelect editor does not submit selected values in the MultiSelect.

 

 

Completed
Last Updated: 04 Jun 2020 13:22 by ADMIN
Release 2020.R2.SP.next
Created by: Lance
Comments: 0
Category: Form
Type: Bug Report
0
DropDownList currently cannot be configured as an editor through the Items configuration of the Form.
Unplanned
Last Updated: 26 May 2020 05:13 by ADMIN
Created by: Javier
Comments: 0
Category: Form
Type: Feature Request
3
Currently, orientation can only be set on the entire Form. In some scenarios, it is required to have a single Form with multiple groups, where each group can have a different orientation setting.

Provide an option to configure orientation per groups.