Kendo UI has the property https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/scrollable that can not be set in the UI for ASP.NET Core with the value TRUE

The reason I am asking is because if I change it on document ready using the grid.setOptions if the grid has autobind then the Read method is executed twice.

Hello,

On Chrome for Android, the dropdown menu appears offscreen. With Firefox for Android or Chrome desktop, it works well.
This sample reproduces the problem : https://runner.telerik.io/fullscreen/@kakone/azuPAHuy. If you click on the right item (user icon), the dropdown appears offscreen.

Be able to bind the DataSource to data without a separate controller and AJAX fetch for use with Razor Pages.

The use case is a shared data source that drives multiple components on a page for example a chart and grid filtered with an auto complete box.

In a grid I can do this:

@(Html.Kendo().Grid(Model.Data)
    .Name("Grid")
    .Columns(columns =>
    {
        columns.Bound(p => p.Description).Title("Description");
        columns.Bound(p => p.RecordCount).Title("Number Sold").Width(130);
        columns.Bound(p => p.TotalValue).Title("Total Value").Width(130);
        columns.Bound(p => p.AverageValue).Title("Average Value").Width(130);
        columns.Bound(p => p.Rank).Title("Rank").Width(130);
        columns.Bound(p => p.RankMax).Title("Bananas").Width(130);
        columns.Bound(p => p.LowerQuartile).Title("LowerQuartile").Width(130);
        columns.Bound(p => p.Median).Title("Median").Width(130);
        columns.Bound(p => p.UpperQuartile).Title("UpperQuartile").Width(130);
    })
    .Sortable()
    .DataSource(dataSource => dataSource
        .Ajax()
        .PageSize(20)
        .ServerOperation(false)
    )
)

Would want to be able to do same with the DataSource like:

@(Html.Kendo().DataSource(Model.Data)
    .Name("dataSource1")
    .Ajax(dataSource => dataSource
        .ServerOperation(false)
    )
    )

Bug report

The StringExtensions -> ToCamelCase method(part of Kendo.Mvc.Extenstions) doesn't return the expected Camel case result.

• More details in ticket # 1458202

Reproduction of the problem

Include the Kendo.Mvc.Extenstions namespace. Define the following in a controller:

        public IActionResult Index()
        {
            string test = "RANDOMStatusId";
            test = test.ToCamelCase();

            return View();
        }

Set a debugger and see the value of the "test" variable.

Current behavior

The returned from the ToCamelCase() method value is "rANDOMStatusId"

Expected/desired behavior

The expected result returned from the ToCamelCase() method value is "randomStatusId"

Environment

• Kendo UI version: 2020.1.219
• jQuery version: x.y
• Browser: [all]

Even when using server side paging some requests can be very long, and may be canceled by the user.  Adding a CancellationToken parameter to the ToDataSourceResultAsync.

Bug report

Validation attributes are not rendered on Kendo editors if ViewData contains same key as the model.

Reproduction of the problem

@{
  ViewData["Title"] = "Home Page"; 
}

@using (Html.BeginForm())
{
  @Html.Kendo().TextBoxFor(model => model.Title)
}

<script>
  $(function () {
    $("form").kendoValidator();
  });
</script>

Current behavior

Validation attributes are not rendered.

Expected/desired behavior

Validation attributes should be rendered on the input element.

Environment

• Kendo UI version: 2020.1.219
• Browser: [all]

The Menu TagHelper does not render correct links for its items when the asp-page attribute is used.

With area it does not render a link at all:
<menu-item text="Home" asp-area="Products" asp-controller="Home" asp-action="About"></menu-item>

Without area it renders an incorrect link
<menu-item text="Login" asp-area="Products" asp-page="/Books"></menu-item>

Hi guys,

I found out, that the QueryableExtension always generates a ToLower for strings filtered with the equals operator. The ToLower is applied by the FilterOperatorExtensions in this method:

    private static Expression GenerateEqual(
      Expression left,
      Expression right,
      bool liftMemberAccess)
    {
      if (left.Type == typeof (string))
      {
        left = FilterOperatorExtensions.GenerateToLowerCall(left, liftMemberAccess);
        right = FilterOperatorExtensions.GenerateToLowerCall(right, liftMemberAccess);
      }
      return (Expression) Expression.Equal(left, right);
    }

It would be nice, if the to lower is controllable with a parameter. At the moment it generates a to lower in the sql query, which generates a lot of overhead in some situations with large tables.

At the moment I remove all "equal to" filter and apply it manually to the IQueryable object.

Best regards

Moritz

Bug report

The overlay is not removed when closing an Alert dialog, if there is an open Window with draggable.containment option set.

Reproduction of the problem

Dojo example.

1. Click the "Alert" button
2. Click "Ok" in the Alert dialog.

Current behavior

The overlay is not removed.

Expected/desired behavior

The overlay is removed.

Workaround: dojo.

Environment

• Kendo UI version: 2020.1.219
• jQuery version: x.y
• Browser: [all]

Bug report

DropDownTreeItemModel does not properly pass its HtmlAttributes members on populating DropDownTree with BindTo()

Reproduction of the problem

In .Net Core application, implement the following view:

@(Html.Kendo().DropDownTree()
    .Name("kendoTreeItems")
    .BindTo((IEnumerable<DropDownTreeItemModel>)ViewBag.Items)
)

and the following controller:

public IActionResult Index()
{
    ViewBag.Items = GetItems();
    return View();
}

public IEnumerable<DropDownTreeItemModel> GetItems()
{
    IDictionary<string, string> attributes = new Dictionary<string, string>
    {
        { "style", "background: red" }
    };

            List<DropDownTreeItemModel> items = new List<DropDownTreeItemModel>
    {
        new DropDownTreeItemModel { Text = "Item 1", HtmlAttributes = attributes },
        new DropDownTreeItemModel { Text = "Item 2", HtmlAttributes = attributes },
        new DropDownTreeItemModel { Text = "Item 3", HtmlAttributes = attributes },
        new DropDownTreeItemModel { Text = "Item 4", HtmlAttributes = attributes },
    };

    return items;
}

Current behavior

The HTML attributes will not be passed to the DropDownTree items.

Expected/desired behavior

The HTML attributes should be passed and present in the DropDownTree items.

Environment

• Kendo UI version: 2020.1.219
• Browser: [all]

### Bug report


### Reproduction of the problem
On the mobile version on Android 10, the Grid does not enter incell editing.

Dojo to reproduce: https://dojo.telerik.com/oDUBuKAt


### Environment

* **Kendo UI version:** 2020.1.219
* **Browser:** Android 10 Web Browser 

Bug report

The PDFViewer HTML helper incorrectly serializes the passed to its "File" configuration URL, when the URL has an ampersand(&) sign in it. In the output of the HTML helper, the ampersand is changed with its ASCII code - "\u0026"

• The issue is reproducible both in the UI for ASP.NET Core and UI for ASP.NET MVC suites.

Reproduction of the problem

1. Create an ASP.NET Core or MVC project
2. Paste the below code in it and run it
   @(Html.Kendo().PDFViewer() .Name("pdfviewer-test") .PdfjsProcessing(pdf => pdf .File("https://myrandomcomain.com/api/MyFolder/GetPDF?reference=xxxxxxxx&param1=0&param2=100&contentType=application/pdf") ) .Height(400) )
3. View the source of the opened page and see the generated Javascript code

Current behavior

The generated code is:
jQuery("#pdfviewer-test").kendoPDFViewer({"pdfjsProcessing":{"file":{"url":"https://myrandomcomain.com/api/MyFolder/GetPDF?reference=xxxxxxxx\u0026param1=0\u0026param2=100\u0026contentType=application/pdf"}},"height":400});

Expected/desired behavior

The expected result is
jQuery("#pdfviewer-test").kendoPDFViewer({"pdfjsProcessing":{"file":{"url":"https://myrandomcomain.com/api/MyFolder/GetPDF?reference=xxxxxxxx&param1=0&param2=100&contentType=application/pdf"}},"height":400});

Environment

• Kendo UI version: 2020.1.219
• jQuery version: x.y
• Browser: [all]

Hello,

At the moment I'm using the ImageBrowser in the Kendo editor.

A user contacted me and reported she would like to browse through the images in the ImageBrowser in a list view instead of tile view (thumbnails with text).

However, I couldn't find a suitable way to achieve this.

Does the current imagebrowser/editor have this functionality and if so, could you help me achieve this please?

Kind regards,

Joran

Bug report

Reproducible in Chrome and Firefox. Not reproducible in IE11.

Reproduction of the problem

Dojo example.
There are two Menus. In the first one navigation is triggered from the function passed to the "Sub Item 2" item's url option. In the second Menu navigation is triggered in the Menu's select event handler.

1. Hover "Item 2" and click "Sub Item 2"
   The wiki page will open in a new tab.
2. Check the Menu in the original tab with the dojo.

Current behavior

Doing this in the first Menu, results in the submenu remaining open.

Expected/desired behavior

The submenu should close in both scenarios, since closeOnClick is enabled by default and the select event fires before triggering the navigation.

Environment

• Kendo UI version: 2020.1.114
• jQuery version: x.y
• Browser: [Chrome XX | Firefox XX]

At current when working with the french culture, the year in the date will default be represented with 2Y (dd/MM/yy)

This potentially creates a problem for dates>2030, a date like 01/01/30 would be save as 1930 instead of 2030. 

When looking at other culture such nl-BE, en-GB, 4 digits are always used for the year.

I propose to change this also for the french culture so that dd/MM/yyyy would become the standard format.

PS: You can download the culture file and change it, but you'd experience a problem with the popup editor in combination with a display template... in this case the local culture file will be ignored and 2 digits would still be used for the date

When a model property is decorated with data annotation attributes, the RadioButton HtmlHelper does not properly render the data-val and data-val-required attributes on the element.

Expected behavior:  Data attributes should be successfully rendered on the <input> element.