Allow customization of the Validation Tooltip position.
For example, positioning the Tooltip based on the cell, on the input.
The NumericTextBox should behave like standard input fields and automatically select all the text when tabbing into the control. This should work for NumericTextBox controls whether using inside or outside of a Kendo grid.
FluentValidation is an excellent tool that keep us from using DataAnnotations' Validator's decorators to achieve the entity class keeps as is, a just POCO class. The pros of this lead us to those developers, like me, that focus its backend (entities) development in Database-First processes, to lose decorators applied to the entity or model view class in every change made to the Database rather than the entity class, FluentValidation give us a better control of the validation rules, separates the validation from the entity class or view model class, testing is easier than DataAnnotations and support client-side validations. As far as I know, FluentValidation injects Data Annotation under the covers.
It would be great if you consider to take advantage of the integration with this tool in your route map.
Every time the user scrolls in a grid with virtual scrolling, the grid asks for the total number of rows satisfying the filtering conditions. This causes the same exact query to be sent to the database multiple times. Instead cache this value and only ask for it if the filters change.
So with normal scrolling down the grid this will generate the following traffic to SQL:
Select Top 100, Skip 0 from Table where...
Select Count(*) from Table where (returns X number of rows)
Select Top 100, Skip 100 from Table where...
Select Count(*) from Table where (returns same X, exact same query)
Select Top 100, Skip 200 from Table where...
Select Count(*) from Table where (returns same X)
and so on
To see this open a copy of the grid with virtual scrolling:
Scroll the grid down:
In Developer Tools observer the result that is sent back to server includes the same:
every time. In terms this will often generate a Select Count(*) being sent to the server in order to supply the answer for the current filters of the grid. An example when a Select count(*) is generated can be seen in your MVC wrappers, for example, where the toDataSourceResult() will cause this same query to repeatedly be sent to the database with every request for new data (use SQL Server Profiler or similiar to see the unnecessary queries). This is also true for your demo implemenations of the server code when used with Kendo UI.
For grids with large data sets, as is often used with virtual scrolling, this can be a slow query.
Instead of asking for the number of rows every time the grid is scrolled, only do so at inatialization and when the filtering conditions are changed (for example use a variable or an event to keep track of the dataSources filters changing).
If the program cannot assume that the same number of rows will be returned, then please implement a setting for developers that we can use to say that the data is not changing.
We look at historical data that are constant and with more than 100k rows, the Select count(*) puts an annecessary strain on the servers.
We could implement caching for this value, but instead the grid should not repetedly ask for the same value multiple times, instead of only when the filters change.
Export to PDF shows the header commands like "Export to PDF", etc. These should be configurable to not be displayed.
Similarly, using a .PdfExport event to hide and show the command columns is functional but should be included as a property to avoid the flashing that the hide/show does to a large element.
I'm resurrecting this on the suggestion of Todd Anglin. An earlier request for this feature was declined because modern browsers include spell check. However, there are many use cases where this is no use. In my particular case I need: - Spell Check to work in IE8 - Custom (and programmatically accessible) dictionaries - The ability to programmatically turn spell check on/off on a field by field basis
When the DateInput uses a day-first format, e.g. dd/MM/yyyy, if you try to type in 29/02 the DateInput auto-corrects it to 01/02, which is not intuitive to the user and requires them to go back and fix the date again after typing in a leap year.
The DateInput should allow the user to type in 29/02 until the year portion is not provided.
We are using the progress functionality across the applications, also its inbuilt in Grids/Tree View or most of the Kendo controls when data is loading. Now we are hit with an Accessibility issue as stated below in JAWS 2019.
"Issue: There is a loading screen that appears throughout the application. Sighted users are able to see the loading indicator, however, screen reader users should also be aware of the loading screen."
this is what we use explicitly in some places other than the inbuilt loading indicator.
// show loading indicator kendo.ui.progress($("#divCriteria"), true);
So is there any settings available that we can make this screen readable when the progress bar appears? meaning if we setup globally once place it takes care across everywhere? Including Grids / Treeview etc.
I read setting this role=” aria-busy=” will do the job, but this functionality already have the kendo scripts?
<div role="alert" aria-busy="alert"> Data is loading... </div>
Appreciate a quick response or solution for this...
I would love it if I could add a header to the PDF when using drawTabularData. I'd like to add some header information (e.g. some text above the table) describing what the PDF contains. Ideally this would repeat on each page of the PDF. For context, I'm using drawTabularData to export data from a Grid component to PDF in a way that supports horizontal page splitting (column splitting).
Provide an option that allows encrypting each chunk of data that is being sent by the Upload.