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.

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.

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

When using the Nova theme locked command columns are not styled correctly.   
In the following dojo one command column is locked and not styled while another command column is not locked but styled correctly.
https://dojo.telerik.com/eWECAZEw

Here's the code in case the dojo doesn't work:

We need the ability to merge grid rows with the same values (see attached). This is a feature our customers have come accustom to with our Windows UI and the Developer Express toolkit. I understand I can manipulate the rowTemplate to achieve similar results but it is my understanding this will cause issues with row selection, editing, etc... Is this something that can be introduced in the future?

Regards,

Bracken

1. Create a grid with two editable columns.
2. Define validation rules for both columns. Keep one column as required.
3. Edit the row. Set the required column value using model.set method.'

It fails because before setting the value it performs validation. If validation was successful then it will set the value on model.

Since the desired field has no value and validation rule will fail on that.

It should accept the value and then perform validation. If validation fails with new value then it might discard the changes.

$("#grid").kendoGrid({
  dataSource: {
    batch: true,
    transport: {
      read: function(e){
        e.success([1,2,3,4,5,6,7,8,9].map(function(i){return {id: i, title: "test" + i}}));
      }
    },
    schema: {
      model: {
        id: "id",
        fields: {
          id: {defaultValue: "-1"},
          title: {
            validation: {
              required: true
            }
          }
        }
      }
    }
  },
  columns: [
    {field: "title", title: "Title", filterable: {field: "title.a"}},
    {command: ["edit", {name: "destroy"}]}
  ],
  editable: {mode: "inline"},
  filterable: true,
  toolbar: [{name: "create"}]
});
 
var grid = $("#grid").getKendoGrid();
var model = grid.dataItems()[0];
grid.editRow(model);
model.set('title', '');
model.set('title', 'test 1111'); // it will fail