Bug report

When using a ForeignKeyColumn that is bound to a dataSource, the Grid options will not be available initially such as during the document.ready event.

Reproduction of the problem

Please visit this Progress Kendo UI Dojo which demonstrates the Grid unable to retrieve the options, and receiving a JavaScript error.

Expected/desired behavior

The Grid options should be available upon the document.ready event with a databound ForeignKeyColumn.

Environment

• Kendo UI version: 2022.2.510
• jQuery version: 3.6.0
• Browser: All

Bug report

Sticky Column misalign on scroll with Safari IOS in Desktop Mode

Reproduction of the problem

Open: https://demos.telerik.com/kendo-ui/grid/sticky-columns

Make sure to "Request Desktop Website" with Safari  (it works fine in Mobile Mode)

Then try scrolling vertically in the grid particularly first dragging the frozen columns and then dragging the non-frozen columns

Environment
Kendo UI version: 2022.3.1109
jQuery version: All Supported Versions
Browser: Firefox 108.0

Bug report

Reproduction of the problem

Open: https://demos.telerik.com/kendo-ui/grid/frozen-columns

Make sure to "Request Desktop Website" with Safari  (it works fine in Mobile Mode)

Then try scrolling vertically in the grid particularly first dragging the frozen columns and then dragging the non-frozen columns

Environment
Kendo UI version: 2022.3.1109
jQuery version: All Supported Versions
Browser: Firefox 108.0

Bug report

Using groupHeaderColumnTemplate in Group Paging causes group rows to render without a group-data-uid attribute

Reproduction of the problem
Dojo example: https://dojo.telerik.com/AzecInaY

Inspect grouping row element

Expected/desired behavior
The group-data-uid attribute shall be present

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

I want to use multi-checkbox filtering with complex datasource. However, the name of the field on which the filtering needs to be applied is not the same as the column field. Thus, in order to avoid custom implementation I would like to have an option to set which is the field that should be used for the filtering.

For example, in the Dojo linked here, I would like to filter the country column, but the filter field in the filterable datasource is 'id'.

Hi Team,

I would like to request a way to control what is included in the ColumnMenu.  For example, a way to remove 'Group/Ungroup' and 'set column position'.  

Thank you!

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.

Is it possible that you include a way to resize rows on a grid like we have the option to resize columns?

My application has a default row height retrieved from database, we do not let the content to overflow this row height. 
But instead we want to give the user the option to manually resize the row to see the full text content.

This row resizing, though it is done only on one row would affect all the rows currently shown.

Bug report

When all columns have set width in pixels resizing of the columns does not work as expected and the cursor is not aligned with the columns.

Reproduction of the problem

1. Open the Dojo - https://dojo.telerik.com/@NeliKondova/uMEqOTEL
2. Try to resize the columns

Current behavior

The column becomes much wider and the cursor is not aligned with the column border - screencast - https://somup.com/c0lqlFkjLc

Expected/desired behavior

The column should be resized along with the movement of the cursor.

Note: The issue starts to appear with Kendo version 2023 R2 SP1 (2023.2.718). Before this version the issue was reproducible only when the pixels are mentioned in the width setting - example: { field: "name", width: "20px" }, - Dojo - https://dojo.telerik.com/@NeliKondova/IdEsagig

Environment

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

Bug report

In a Grid that has locked columns, if you tab through the content and then tab back using Shift-Tab, the first column is not completely visible when you reach it.

Reproduction of the problem

1. Open this Dojo example - https://dojo.telerik.com/eKuKoFaN
2. Navigate through the first row using Tab key.
3. Navigate back to the cell in the CustomerID column using Shift+Tab

Current behavior

The column, including the header, is not completely visible.

Expected/desired behavior

The whole column should be visible.

Environment

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

Hi,

I've found a bug in the jQuery template code for Kendo Grids. Seems that it directly injects the name of a field from the data source results under the assumption that the field name is a valid JavaScript identifier (i.e. data.someIdenifier). But when the data source results contain a field name that is a number (as in my case), this results in invalid JavaScript (i.e. data.1234) and causes the Kendo Grid code to error. I notice that in some places in the template code, indexing is used instead of member access (data['someIdentifier'] instead of data.someIdentifier), but not everywhere. I'd recommend using indexing every where to fix this (i.e. data[1234]).

Bug report

The behavior has been introduced in R3 2020.

Reproduction of the problem

Dojo example.

1. Run the example

Current behavior

The sticky column's left border is not displayed.

Expected/desired behavior

The sticky column's left border is displayed.

Environment

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

Hi Team,

I would like to request the functionality for the Kendo UI Grid with row filter mode to include composite filtering.  

Thank you!

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 ]

Bug report

When a column is unsticked either through the built-in context menu or through the unstickColumn method all the casses from the cells in that column are removed, even the 'k-table-td' class.

Reproduction of the problem

1. Open the Dojo and inspect the cells in the ShipAddress column
2. Unstick the column

Current behavior

All classes in that column are removed

<td class="" style="" role="gridcell">Boulevard Tirou, 255</td>

Note: Initially the cells have the k-table-td class twice which is also not expected

<td class="k-grid-content-sticky k-table-td k-table-td" style="left: 0px; right: 0px;" role="gridcell">Boulevard Tirou, 255</td>

Expected/desired behavior

Only the 'k-grid-content-sticky' class should be added or removed when sticking/unsticking a column.

Environment

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

Bug report
Аggregates not working in group footer, when string value contains line break "\n"

Reproduction of the problem
Dojo: https://dojo.telerik.com/uPuyEcEJ

Current behavior
Аggregates not working

Expected/desired behavior
Aggregated should be working fine when the value contains "\n"

Environment
Kendo UI version: [all]
Browser: [all]

Bug report

columns.field.filterable.cell.inputWidth does not apply since R1 2022

Reproduction of the problem

Dojo: https://dojo.telerik.com/oVILIzaW

Current behavior
Width of autocomplete input is not affected

Expected/desired behavior
Width shall be reflected

Workaround

Environment
Kendo UI version: 2022.2.621
Browser: [all]

Title: Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key.

Description: Keyboard users will be impacted here , as focus is getting lost after closing the filter pop-up.

Environment (OS, Application):

Test Environment:

OS version (OS Build 22000.856) 

Microsoft Edge : Version 105.0.1343.25 (Official build) (64-bit) 

URL: https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/filterable

Repro Steps:

1. Open given URL in Edge Dev. 

2. "Kendo UI for jQuery" page will be open.

3. Navigate to "Preview" button present under filterable.

4. Navigate to the filter controls present on the table.

5. Activate the filter control using mouse and navigate over the pop-up.

6. Press 'Escape' key on the flyout and Verify that Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key or not

Actual Result: 

Keyboard focus loss is observed after closing the filter pop-up by 'Esc' key.

On pressing Tab key further focus start moving from "Related Properties" link.

Expected Result:

Keyboard focus loss should not be observed after performing any action on the page and should restore on the control which has been activated, here after pressing 'Esc' key, focus should restore on 'Filter' button only.

Dear Kendo-Team,

When using the less-based Bootstrap theme, the PDF export of a grid shows strange borders underneath header's column menus. Refer to the following DOJO for replication:

https://dojo.telerik.com/ePOSiluT

Enclosed you will find a screenshot of the PDF export, showing the strange borders.

Is this something we can easily (temporarily) fix on our own by adjusting some CSS styles?

Bye

Ralf