Completed
Last Updated: 15 Aug 2019 12:21 by ADMIN
Created by: Scott Waye
Comments: 4
Category: Grid
Type: Feature Request
32
Allow customisation of the bool filter in grids.  I.E. implement the UI property that works for other non-checked columns.  The current filter is too wide, does not allow fontawesome characters, etc.
Pending Review
Last Updated: 12 Aug 2019 18:59 by Chingis
Created by: Chingis
Comments: 0
Category: Grid
Type: Feature Request
0

Request

I'd like to ask for a demo which utilizes the most up to date approach to creating a Kendo UI Grid using NPM, TypeScript, and in a SharePoint 2019 with a Gulp serve environment. 

Thank you for your consideration!

Approved
Last Updated: 12 Aug 2019 10:23 by ADMIN
For performance reasons, we would like to only show the group headers collapsed when first grouping, and only add its child rows when expanded. This is done for hierarchical grids and minimizes unnecessarily large DOMs for data the user will never look at. 
Under Review
Last Updated: 06 Aug 2019 06:36 by Christian
Created by: Darryl
Comments: 4
Category: Grid
Type: Feature Request
32
Personally, I much prefer image buttons over text buttons in the grid just to keep bulk down especially when you have a wide grid or a number of custom command buttons with long text.

To do this at present requires some fancy css styling in the grid databound event.

I would like to see more configuration options for grid commands to allow for ....

- Built-in commands (Edit, Delete, etc) and custom commands to be image only
- Built-in commands and custom commands to have a "tooltip" option
Pending Review
Last Updated: 01 Aug 2019 13:58 by David
Created by: David
Comments: 0
Category: Grid
Type: Feature Request
0

Please consider adding groupHeaderColumnAttributes as a feature. groupHeaderColumnTemplate is a welcome addition to the grid capabilities and it would be great to easily set styles on group header columns. Frankly, it would be helpful to have attributes available for templates (groupHeader, groupFooter, etc.).

 

Thanks

Approved
Last Updated: 31 Jul 2019 13:35 by ADMIN
Created by: Jon
Comments: 1
Category: Grid
Type: Feature Request
7
When using Frozen columns in the grid, the frozen column is not usable for vertical scrolling when used in a mobile application. 

This means that it is not possible to swipe up and Down on the frozen column to scroll the grid vertically. This again makes the user experience very odd (actually it feels like a bug), because it is not natural to have to use the other, none froze columns, to be able to scroll vertically.

Thanks!

Jon
In Development
Last Updated: 29 Jul 2019 07:11 by ADMIN
Created by: Raymond
Comments: 1
Category: Grid
Type: Feature Request
4
It would be nice to have the option for a single filter input that searches all columns on the Grid.  I was able to implement my own custom solution but having to apply that to every grid in my app is cumbersome.

I understand the importance for the flexibility side of having each column with its own filter box, but for simpler apps this is overkill and a single filter box is enough.  The column component already has the [filterable] flag so this can possibly be used to exclude any columns if necessary.

I was thinking of something similar to what is an out of the box feature for the Datatables JS plugin

https://datatables.net/

Default search box that searches everything.  Very simple to use and understand for basic users or when your application only calls for something that simplistic.
In Development
Last Updated: 29 Jul 2019 07:04 by ADMIN
Created by: Tino
Comments: 2
Category: Grid
Type: Feature Request
11
Please add out of box functionality ( MVC and Kendo ) for simple search panel like DevExpress : 
http://demos.devexpress.com/MVCxGridViewDemos/Filtering/SearchPanel
In Development
Last Updated: 29 Jul 2019 07:01 by ADMIN
Created by: Michael
Comments: 2
Category: Grid
Type: Feature Request
2
Multiple String searching in standard filter.

Today the basic Grid filter for strings can be used to search for 1 or 2 items at best.  It would be great to be able to filter for > 2 items from 1 column at a time.  

A multicheck box filter does not work so well when you have 100k+ items, and the multicheckbox ends up with 1000s of items in it.  A string search is more appropriate for the end user.

Our current grid a user can filter for upwards of 500 strings of text in one column by treating the input as a textarea that is styled to auto-grow and is not resizable.
Pending Review
Last Updated: 26 Jul 2019 08:43 by ADMIN
Let's say we have an grid with incell editing and navigation enabled. But also there may be some column which are readonly (non editable ).  Currently when I press the tab from an editable cell it focus on non editable cell's ,which is no needed. I'll prefer to have a navigation which is stopping only at the editable cells when I press the tab.  And also I would like to add new row when I press the tab form last editable cell in the last row.
Pending Review
Last Updated: 18 Jul 2019 12:01 by ADMIN
Currently, if you use alwaysVisbile=false, the pager disappears on each grid rendering and it's very annoying for the end user. Another strange thing about this pager is the way the logic works behind. If the rows are equal to the page number of rows, currently you'll see the pager, but in fact you don't need it. 
Approved
Last Updated: 03 Jul 2019 15:30 by ADMIN
Created by: Johann Meyer
Comments: 0
Category: Grid
Type: Feature Request
3
The new event should fire as soon as the grid is fully rendered und ready to take user input or focus.

We need this for automated UI Testing. SetTimeout does not work reliable.
In Development
Last Updated: 26 Jun 2019 01:44 by Jeffrey
Created by: Sean
Comments: 15
Category: Grid
Type: Feature Request
73
The ability to export a grid to excel has been a great addition, we would like the ability to export in CSV and XML also.
Approved
Last Updated: 04 Jun 2019 14:02 by ADMIN
Created by: Michael
Comments: 1
Category: Grid
Type: Feature Request
0
When using a screenreader in navigate mode the grid does not announce that the column headers are links that can be used to sort the table.  There are aria-label tags added when a grid grouping function is active (like the demo at https://demos.telerik.com/kendo-ui/grid/keyboard-navigation), but there is no aira-label text to indicate the sorting behavior. 
Approved
Last Updated: 17 May 2019 12:44 by ADMIN

We need a way to disable the _step function (kendo.web.js) from being run whenever keying up or down in a nullable NumericTextBox grid column. Without this, moving between cells is setting the value of the cell being stepped out of to zero despite no text/numerical input. Our workaround was to override the Kendo JS to skip the majority of the _step logic by checking for whether spinners were disabled:


if(that.options.spinners === false) {
	return;
}

 

See support ticket logged for further information and code/video example: https://www.telerik.com/account/support-tickets/view-ticket/1408355

Approved
Last Updated: 16 May 2019 17:05 by Tsvetina
It seems that you would want to conditionally have clearSelection() behave differently with persistSelection enabled, as it does not clear the selection of items on other pages. At the very least offer us a clearAllSelections() method if modifying the behavior of the other method is not desirable.
Approved
Last Updated: 09 May 2019 08:55 by ADMIN

Hi,

The Kendo UI Grid has the ability to conditionally hide/show the command columns. But in order to hide some buttons from the toolbar, you need a dataBound handler. It will be useful to hide the "Create" button from non-admins, but be able to show the PDF and Excel Export or hide the entire toolbar.

toolbar: [
    { name: "create", visible:function(){ return isAdmin; } },
    { name: "reports" , visible: function(){ return isManager }},
    { name: "cancel" }
  ],

Currently, we need to use this dataBound handler:

.Events(e=>e.DataBound("onDataBound"))     
  
 function onDataBound(e) {
   if (true) { // the condition against which you want to show/hide the toolbar
     this.element.find(".k-grid-toolbar").hide(); // hides the entire toolbar
     this.element.find(".k-grid-add").hide(); // hides just the Create button
  }
}


Thank you in advance,
Ken

Pending Review
Last Updated: 01 May 2019 10:01 by ADMIN
Created by: vladan strigo
Comments: 6
Category: Grid
Type: Feature Request
4
We have a problem when working with grid in batch edit mode which puts different fields in the In cell edit mode.

The problem is that cell that are not edited (for example you create a new row, edit only the first field, press save) are never validated. This is of course because they never went into edit mode, so the control and validation was never rendered.

Please give us a feature for such scenario.
Pending Review
Last Updated: 24 Apr 2019 12:29 by ADMIN

 

When endless scrolling and grouping is enabled on the KendoUI grid, collapsing large groups causes the grid to load ALL the hidden detail rows into the DOM.

 

This takes a very long time for the grid to do, as well it violates the whole point of a paging system. (ie I only want you to load X records at a time). Afterwards the performance of entire website (including the grid) will be very poor since potentially thousands of rows have been loaded into the grid and then immediately hidden. Additionally, these rows do not add any value to the user, since they are all hidden anyways.

 

When a category is collapsed, the grid should NOT add any new rows for that category to the DOM.

 

I have included a sample that demonstrates the performance issues.

Declined
Last Updated: 12 Apr 2019 08:31 by ADMIN

We are working on enterprise product, which uses Progress Telerik jQuery KendoUI components extensively purchased by our Company. In which Kendo grid is used in many modules of our product.

Now a days we are working on Accessibility (i.e. keyboard and screen reader) as part of out-of-box feature of our product.

The grid has been made accessible so that it can be navigated using the keyboard arrow keys, once it receives focus via Tab Key in order of tab index or Alt + W short cut key. In turn, this has spawned up one issue in terms of keyboard operatibility. You can now tab into the grid, use arrow keys to navigate to the cell containing action buttons and then again tab to the button that you want to activate.

This is causing confusion in terms of use of the tab key. Ideally, the tab should take focus from one widget to another. That is the tab key should have taken focus into the grid and pressing it again should have navigated away from the grid. But because of the action buttons displayed within the grid for each record, that tab also navigates controls within the grid widget. This causes numerous press of the tab key just to traverse past the grid widget.

Now due to this, user needing to press the tab key multiple times is an accessibility issue.

Also while referring Grid control demo on https://demos.telerik.com/kendo-ui/grid/editing-inline , we found the same type of behavior when traversing through “Edit” and “Delete” buttons. One of the code snippet developed by us using dojo.telerik.com can be referred on https://dojo.telerik.com/@chiragvidani/ulOzaniX/2

It would be great if this issue is addressed with a good accessible way.

 

Please find below reply received from on the accessibility forum, when we tried raising the issue to find out the remedial solution:


Reply 1 by "Glen Walker"

Just to make sure we're talking about the right type of component, a grid vs a table, a grid is like a spreadsheet where you can interact with all the cells.  I agree that a grid should be a single tab stop so that you can easily navigate to the elements after the grid.  However, I have seen implementations that once you're in the grid and in "edit mode", you can tab amongst the cells.  This is helpful if the cell contains an element that uses the arrow keys (such as a radio or select) and you want the arrows interpreted by the element and not navigate to the next cell.  You then need to get out of "edit mode" (perhaps via the escape key) in order to tab off the grid.

A table, on the other hand, doesn't let you interact with the cell directly but that doesn't mean a cell cannot have an interactive element.  That is, you can have links or buttons or inputs in a table cell and it'd still be considered a table and not a grid.  It's kind of a fine nuance.  A grid lets you interact with the cell itself and a table might let you interact with an element that is in the cell, but not with the cell itself.

There is, of course, more to this than that but I was trying to keep it basic and simple.

So, that being said, do you really have a grid or a table?

Let's say you really have a table instead of a grid, and that one of the cells in your table has several buttons, and that pattern is repeated on every row.  You would indeed have a bunch of tab stops, making it difficult to navigate beyond the table.

One possibility is if all the button actions are grouped together, they could be considered a toolbar.  A toolbar is one tab stop and you arrow between the buttons, but you'd still have the problem of having a toolbar on every row.  A toolbar would reduce the number of tab stops compared to having all separate buttons but you'd still have X number of tab stops for X rows.  One for each toolbar.

Maybe a grid in that case would be better.  Tab to the grid, tab again to whatever element follows the grid.  Tab back to the grid and use the arrow keys to navigate to the desired row.  Maybe the row goes into "edit mode" automatically when it receives focus with the arrow and then all the interactive elements in the row get a tabindex of 0.

That might be a bit non-standard and there probably isn't a good "role" to explain the behavior.  A bit of usability testing might be required.

 

Thanks,

Chirag Vidani

  
1 2 3 4 5 6