I'd like the ability to choose the behavior of mutli-row selection on a virtual grid with persisted selection.

 

For purpose of example, assume we have a virtual grid with 50 rows (pager controls not shown), a page size of 10, and persisted selection.

1. Select row 1 on page 1.

2. Scroll down to trigger page 2 to load (rows 11-20).

3. Select row 11, page 2.

4. Current Behavior: Both row 1 and row 11 remain selected.

5. Desired Behavior: Only row 11 remains selected.

 

Reasoning: I believe that a virtual scrolling grid should have selection behavior identical to a single page. That means that the only way to add rows to the selection is holding down control/shift during selection. In other words, on page 1 of the above example, if I select row 1, then row 2, only row 2 remains selected. If I select row 1, then Ctrl+click/Shift+click row 2, both remain selected. For virtual scrolling where multiple pages are displayed fluidly as if a single page, it seems odd to have the selection behave differently.

Bug report

Reproduction of the problem

Dojo example.

1. Drag the page splitter to resize the screen and see the Grid's pager correctly switch between the different responsive styles (expected)
2. Click the "Open Modal" button, which opens a Kendo Window with another Grid in it
3. Drag the page splitter and/or resizing the Window to see each of the Grid's paging styles changing accordingly (expected)
4. Close the Window (destroy is called in the deactivate event handler)
5. Try again to drag the page splitter to resize the screen. This time, the Grid's pager is no longer responsive

Current behavior

Responsiveness of the pager of a Grid declared outside the Window is affected by the Window's destroy method.

Expected/desired behavior

Calling the destroy method has no unexpected effect on components that are not nested in the Window.

Environment

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

Hello, the Excel Export doesn't export the columns headers sums (view in image).

Is it possible export to Excel columns headers sums?

Bug report

When the Kendo UI Grid is paged and the Search panel input is focused, the page is automatically switched to the first one.

Reproduction of the problem

1. Navigate to the live demo:

https://demos.telerik.com/kendo-ui/grid/search-panel

2. Change page to 2 (for instance).

3. Focus the Search panel input.

4. The page is changed to the first one.

Expected/desired behavior

When the search panel is empty and only focused, the page should remain the same.

Environment

* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [ IE 11.768.17763.0] 

While the grid pager is enabled, if set a new datasource of this grid via javascript ( grid.setDataSource(new kendo.data.DataSource(obj)) ), multiple pager numbers wrapper wil be created. And this makes pager layout wrong.

Bug report

Regression introduced in R3 2019 SP1. Reproducible with the LESS themes.

Reproduction of the problem

Dojo example.

1. Open a column filter menu and click on one of the dropdowns in it.

Current behavior

All of the text in the filter menu gets selected.

Expected/desired behavior

No text selection.

Environment

• Kendo UI version: 2019.3.1023
• jQuery version: x.y
• Browser: [Chrome 77 | Firefox 69 ]

• Create e.g. local data grid (id, name)
  
• add 2 records => { id: 1, name: "null", id: 2, name: "Jack" }
• Name column for id = 1 is empty

I have tested this on your example for local data grid. It can be applicable also for remote grid, treelist, etc.

 

I try to use new search panel with server side pagination, but it do not work properly.

Currently, you cannot disable all columns in the column menu - it requires that at least one column is enabled.

However, if the grid contains any non-hidden columns which have IncludeInMenu=false, then it should be possible to disable all the remaining columns using the column menu.

 

 

If you configure a Kendo Grid with client-side paging, each time you call setDataSource to update the data source then a new .k-pager-numbers-wrap DIV is added to the page controls. I've replicated the problem in Dojo at https://dojo.telerik.com/UTolOzer by taking a basic client-side paging demo, moving the dataSource configuration into a separate function (with data("kendoGrid").setDataSource), and calling that function 25 times. At the end, the source shows the UL element with the page buttons inside 25 .k-pager-numbers-wrap DIV elements.

I first noticed this problem because in my own environment, each nested DIV was shifting the page buttons left 1 pixel and overlapping the "previous page" buttons. In my Dojo example, with 25 nested DIVs the page buttons disappear completely.

I've added the following in my own code as a workaround in the dataBound event of the grid:

                            var trueParent = e.sender.pager.element.find(".k-pager-numbers-wrap").first();
                            e.sender.pager.element.find("ul").appendTo(trueParent);
                            trueParent.find(".k-pager-numbers-wrap").remove();

 

Hi.

kendoGrid Pager has a feature of disabling focus of pager arrows with a tabindex="-1".

I was able to override this behavior in some cases. But sometimes it becomes tricky to override this behavior.

My question is:

"Is it possible to disable this behavior, not to override it but really disable. Or if not - maybe you have plans to add such an option in the future (maybe I can submit to the feature updates somewhere)?"

I'd like to request the functionality to change the multiple selection process of the Kendo UI Grid to be the same as Excel.  For example, the following shows a block of cells selected instead of all of the cells in-between the selected cells from Shift+Clicking:

Thank you!

At the moment only the Kendo UI Grid with enabled mobile option will generate a header which can react to the touch and hold gesture.

This makes column resizing impossible when a web grid is used on mobile/tablet. Can you check internally if the grid is used on a mobile browser and create the mobile headers that work with the touch and hold gesture even when the grid does not have the mobile property enabled. This should work out of the box for all grids:

https://docs.telerik.com/kendo-ui/controls/data-management/grid/appearance/adaptive#resizing-of-columns

As followup on Ticket ID: 1431527 screenshots and sample code provided.

"The GridColumnBuild does not have an implementation for the Locked functionality against the dynamic type. The class that gets serialized and sent to the client-side would not have a property for the locked column, therefore, there would be no locked columns."

Can you please examine this functionality?

 

Best,

Peter

Hi, we use the grid "toolbar" property.  But, we found that the documentation of the kendoToolBar "standalone" offers more possibilities, like adding a type "separator", groups, toggle, ...

My question is:
When I create my grid, is it possible to get a reference to its containing kendoToolBar (if it's a complete kendoToolBar ?), that allow to add more complex items.

Something like: 

var kgrid = $('#grid1').kendoGrid({toolbar: [...]}).data("kendoGrid").

var kToolbar = $('#grid1 .k-grid-toolbar').data("kendoToolBar") // or kgrid._secret_property?

kToolbar.add({type: "separator"})

I tried that, but the kToolbar is undefined.

 

Hiding the first column in Grid will show a 2 pixels left border instead one.

Dojo Sample to replicate the issue: https://dojo.telerik.com/ubaLiYEN

Steps:

1. Hide the first column (OrderID) from the Column Menu.

2. Notice the doubled left-border on the left hand side of the Grid.

We have a project where we need the infinite scroll, column sorting/filtering, and remote data enabled.  We are having some issues with sort and filter.  For quick reference, I used the grid demo and changed it to reflect our configuration.  The problem is the grid fires the read command twice when we have loaded more than one page of data. No issues when we have only loaded the first page.

https://dojo.telerik.com/UDoREFID

To reproduce:

1.  Open Chrome

2.  Load the page

3. Hit run

4. Open Developer Tool

5. Switch to the Network tab and filter by XHR only  

7. Click ProductName to sort. There is only one AJAX call.

8. Scroll to the bottom so it loads the next page. It made two AJAX calls

Hi Team,

 

We are have gone through the documentation for make specific column editable. We found that we need to make it in schema. As we are using some complex objects along with ODATA expand.

We are unable to maintain or Add all the fields under schema.If we make a editable property of column to Boolean and based on value framework will me either read-only or editable.

 

Consider a scenario like Grid with 10 columns based on quantity, price,discount change need to calculate the tax.

Here tax calculation will be dynamic and some columns we can add on the fly.

In some cases like ODATA expand  if i want to make expanded column to editable then it a tough process to edit

like above situations it will be useful if we make column editable to Boolean for achieve column level editing

 

Thanks

Dear Sir / Madam,

At grid PDF export, in case of allPages: false --> Actual rows are rendered to multiple pages properly, but all pages are written on the first page.

It works well, if I set "options.pdf.multiPage" to "true", but it is not in API reference.

A solution might be if this variable is fixed to true in grid prototype "saveAsPDF" function:
          "options.multiPage = true;" instead of "options.multiPage = options.multiPage || options.allPages;"

Please see this example: https://dojo.telerik.com/usUnUziL/2

Step 1: press "Export to PDF" --> Result: wrong pdf

Step 2: press "Set multiPage: true"

Step 3: press "Export to PDF" --> Result: good pdf

 

Best Regards,

Szabolcs Tóth

When the grid is configured for InCell editing and frozen columns, it is expected the first editable cell to be opened for editing when a new record is added. 

However, when there is not an editable cell in the locked columns, it would not search in the main content. Here is an example:

https://dojo.telerik.com/ucEraQOW

A temporary workaround would be to override the editModel function and check in the second table as well:

https://dojo.telerik.com/aJEsAnud