Completed
Last Updated: 16 Sep 2019 14:23 by ADMIN
Release 2019.R3

Bug report

The toolbar.click is not serialized correctly when a custom button is added to the ToolBar of the widget. Thus, the click event is not being executed.

Reproduction of the problem

@(Html.Kendo().PDFViewer()
    .Name("test")
    .PdfjsProcessing(pdf => pdf.File(""))
        .Toolbar(t => t.Items(i =>
            {
            i.Add().Name("Open").Id("Open").Command("OpenCommand").Type("button").Icon("folder-open");
            i.Add().Name("Print").Id("Print").Type("button").Icon("print").Click("onPrintClick");
        }))
        .Height(500)
)

<script>
   function onPrintClick(e) {
        alert(e);
    }
</script>

Current behavior

toolbar is not serialized correctly.

Expected/desired behavior

toolbar.click should be serialized correctly.

Environment

  • Kendo UI version: 2019.2.516
  • Browser: [all]
Completed
Last Updated: 22 Oct 2019 12:21 by ADMIN
Created by: Kornelius
Comments: 1
Category: MultiSelect
Type: Bug Report
1
  • Regression report
    Introduced in 2019.2.514.

Current behavior

margin-left causes selected items on second + rows in the MultiSelect to appear unaligned to the items in the first row.

Expected behavior

Reproduction

Dojo example.

What is the motivation or use case for changing the behavior?

Regression

Environment

  • Kendo Ui for jQuery

Browser:

  • Chrome (desktop) version XX
  • Firefox version XX
  • Edge version XX
Completed
Last Updated: 10 Oct 2019 14:34 by ADMIN
Release 2019.R3.SP.next

Bug report

Regression introduced in R2 2018.

Reproduction of the problem

The mobile mode of the Scheduler must be turned off.
Reproducible in the demos.

  1. Tap, hold and try to move an event

Current behavior

The moveStart event does not fire and the event cannot be moved.

Expected/desired behavior

The moveStart event fires and the event can be moved.

Environment

  • Kendo UI version: 2019.3.917
  • jQuery version: x.y
  • Browser: [Android]
Completed
Last Updated: 23 Oct 2019 08:34 by ADMIN

Hi,

I'm experiencing a bug with the kendo grid. In my project I have a rather complicated website where a kendo grid is loaded depending an multiple criteria which can be chosen by the user through dropdowns and multiselects. Luckily, I could break it down to a simple test website and the bug still is bugging around ;)

Description: Depending on the criteria chosen, the grid loads different data which reach from zero to thousands of data rows. In my example here, it's either zero or 100 data rows (depending on the dropdown, if there is either "Empty" or "Not empty" selected). The grid loads its data if you press the button ok (by calling the Load action on the server). The result is meant to be limited to paging of 25 rows (no user choice wanted)!

Heres the code for the cshtml site:

<!DOCTYPE html>

<html>
<head>
    <meta name="viewport" content="width=device-width" />
    <title>Index</title>
</head>
<body>
    <div id="content">
        <div>
            @(Html.Kendo().DropDownList()
                            .Name("test_selector")
                            .DataTextField("Display")
                            .DataValueField("Value")
                            .BindTo(new List<DropDownVM>() {
                                            new DropDownVM()                                                                    {
                                                Display = "Empty",
                                                Value = "empty"
                                            },
                                            new DropDownVM()                                                                    {
                                                Display = "Not empty",
                                                Value = "notEmpty"
                                            }
                            })
            )
        </div>
        <div>
            @(Html.Kendo().Grid<MyProject.ViewModels.Test.TestItem>()
                                            .Name("grid_Test")
                                            .Columns(columns =>
                                            {
                                                columns.Bound(x => x.TestId).Title("TestId").Width(75);
                                                columns.Bound(x => x.TestName).Title("TestName").Width(75);
                                            })
                                            .Sortable()
                                            .Pageable()
                                            .DataSource(dataSource => dataSource
                                                .Ajax()
                                                .PageSize(25)
                                                .Read(read => read.Action("Load", "Test").Data("GetSelectorData"))
                                            )
                                            .AutoBind(false) //Do not load Grid data initially
            )
        </div>
        <div>
            @Html.Kendo().Button().Name("Load").Content("Load")
        </div>
    </div>
    <script type="text/javascript">
        $("#Load").on("click", function (e) {
            var grid = $("#grid_Test");
            grid.data("kendoGrid").dataSource.read();
        });

        function GetSelectorData() {
            var selectorData = {
                type: $('#test_selector').data("kendoDropDownList").value()
            }
            return selectorData;
        }
    </script>
</body>
</html>

And the corresponding controller:


public class TestController : BaseController
    {
        public ActionResult Index()
        {
            return View();
        }

        public ActionResult Load([DataSourceRequest] DataSourceRequest request, string type)
        {
            List<TestItem> result = new List<TestItem>();
            if (type == "notEmpty")
            {
                for (int id = 1; id <= 100; id++)
                    result.Add(CreateTestItem(id));
            }

            request.PageSize = 25;
            return Json(result.ToDataSourceResult(request));
        }

        private TestItem CreateTestItem(int id)
        {
            TestItem result = new TestItem()
            {
                TestId = id,
                TestName = "Name" + id
            };
            return result;
        }
    }

Problem: The scenario described above works actually fine as long as the grid gets at least one data row delivered as DataSourceResult (i.e., result.Count > 0 in the Load method of the controller). The request object in the controller's Load method also shows request.PageSize to be configured to 25. Also, if I choose "Empty" from the dropdown and press the Load-button, the request in the controller will show PageSize = 25. But if I switch the selector to "Not empty" afterwards and press Load, the request will show PageSize = 0! This results in the grid not being paged at all and showing all results on a single page (which leads to serious connectivity problems in my productive project as soon as there are several thousands of data rows).

I tried a quick workaround in the Load method of the controller by setting the PageSize manually back to 25 (which is not wanted of course, but would actually work for me at the moment):


public ActionResult Load([DataSourceRequest] DataSourceRequest request, string type)
        {
            List<TestItem> result = new List<TestItem>();
            if (type == "notEmpty")
            {
                for (int id = 1; id <= 100; id++)
                    result.Add(CreateTestItem(id));
            }

            request.PageSize = 25;
            return Json(result.ToDataSourceResult(request));
        }

Unfortunately, this doesn't work either. The paging will be back on again and there will be only 25 data rows loaded in the grid but there is only one single page no matter how many data rows are loaded (see attached screenshot).

Do you know about this? Unfortunately I couldn't find any help for this problem so far.

Greetings!

Completed
Last Updated: 13 Nov 2019 15:09 by ADMIN
Release 2019.R3.SP.next

Bug report

If the CurrentTimeMarker is enabled (it is by default), the resources are grouped, and events with different resource values (about 70) are loaded for the current day, a significant performance deterioration is observed.
With the CurrentTimeMaker disabled or the events loaded for a date different than today (past or future) the performance issue is not exhibited.

Reproduction of the problem

MVCSchedulerCurrentTimeMarker.zip

  1. Run the attached sample project.

Current behavior

No exceptions are thrown, but the Scheduler becomes unresponsive.

Expected/desired behavior

There should be no performance hit, regardless of CurrentTimeMarker being enabled/disabled.

Environment

  • Kendo UI version: 2019.3.917
  • jQuery version: x.y
  • Browser: [all]
Completed
Last Updated: 11 Nov 2019 07:54 by ADMIN
Release 2019.R3.SP.next
Created by: Ikbum Kim
Comments: 1
Category: Grid
Type: Bug Report
0

When I use lock column, margin is created in the right scroll of the grid. Did you know this problem?
How can I fix this problem? 

 

 

Completed
Last Updated: 14 Feb 2019 14:49 by ADMIN
Created by: Kevin
Comments: 1
Category: UI for ASP.NET MVC
Type: Bug Report
0

Hi,

I notice that some of the styling has changed for the Blue Opal theme in the latest release (2019 R1), notably the background colour of the selected page on the grid and the already selected items on a Drop Down List have gone from dark blue to a bright blue (see attached screenshots from demos.telerik.com).

Is this by design or by mistake?

Particularly on the drop down list, this change makes it more difficult to identify the already selected items.

Can this go back to what it used to be - or is there a way of manually changing this setting via the site.css?

Thanks

Kevin

 

 

 

Completed
Last Updated: 13 Jun 2019 08:08 by ADMIN
Release 2019.R2.SP.Next
Created by: Sergey
Comments: 0
Category: ComboBox
Type: Bug Report
0

Bug report

ComboBox with filtering option set to "contains".

Search for the last element in ComboBox dropdown and select it. Delete the selected item with mouse selection and "Delete" button. The dropdown will open again. Select the first element in the dropdown. It will close and no data will be selected. If we repeat the scenario and instead of selecting the first element, we select another one, everything is working properly.

This is regression introduced in 2018 R1 SP1

Reproduction of the problem

  1. Open this Dojo and run it
  2. Select the ComboBox and enter "rib", then select "Rib Knit"
  3. Unfocus the ComboBox and then focus it again
  4. Using the mouse select the "Rib Knit" text and delete it. The dropdown of the ComboBox will open.
  5. Select the first element "Cotton".
  6. The dropdown closes and no item is selected

Current behavior

Please check this demo video.

Expected/desired behavior

Please check this demo video

Environment

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