Bug report
When the horizontal scroll of the grid is shown and is configured for RTL, the resize handle is mispositioned.
Reproduction of the problem
1. Make the grid scrollable and set explicit widths to all columns.
2. Make the grid RTL.
3. Introduce multi-column headers.
4. Notice that the columns cannot be resized due to the disposition of the handler.
5. Dojo for replication:
https://dojo.telerik.com/IZInOVUd
6. Notice that whenever the horizontal scroll is not present, the resize handle is positioned correctly.
Environment
* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [all]
Hi,
the adaptive rendering in the grid control is not working in the current version(2019.3.1023).
To reproduce go to https://docs.telerik.com/kendo-ui/controls/data-management/grid/appearance/adaptive#configuring-panes-on-mobile --> Open in Dojo --> Run and the 2 rows are not displaying. If you switch to version, choose Library dropdown, 2018.3.1017 or up to 2019.1.220 the 2 rows are ok.
Similar behaviour is inspected to the scheduler control agenda view. To reproduce go to https://docs.telerik.com/kendo-ui/controls/scheduling/scheduler/adaptive-rendering#configuring-panes-on-mobile --> Open in Dojo --> Run --> change view from week to Agenda and the 2 events are not shown. If you switch to version, choose Library dropdown, 2018.3.1017 or up to 2019.1.220 the 2 events are ok.
Tried in chrome, safari and mobile phones.
thanks,
Kostas Vlachakis
Excel files generated by Kendo Excel Export cannot be imported by the MS ODBC Driver. The error reported in this forum thread is: External table is not in expected format.
If the file is opened and resaved with Excel or if the styles.xml file is replaced with any styles.xml generated by MS Excel, the error does not occur. When compared the styles.xml of Excel does not contain a numberFormat, no other obvious major differences at first glance:
E.g.:
<numFmts count="2">
<numFmt formatCode="#" numFmtId="165" />
<numFmt formatCode="#" numFmtId="166" />
</numFmts>
If possible, modify the styles.xml template to enable seamless use with OleDB
Regression introduced in 2019.2.619.
Related commit: telerik/kendo@2a806f6#diff-f810c335b76ea2e4d78327457f230a46L3882-R3882
Dojo example.
The following validation message is displayed: ! name
The validation message should be: ! name is required
Dojo example.
Responsiveness of the pager of a Grid declared outside the Window is affected by the Window's destroy method.
Calling the destroy method has no unexpected effect on components that are not nested in the Window.
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]
Regression introduced in R3 2019 SP1. Reproducible with the LESS themes.
All of the text in the filter menu gets selected.
No text selection.
I have tested this on your example for local data grid. It can be applicable also for remote grid, treelist, etc.
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();
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.
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:
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:
<!DOCTYPE html>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
Hi,
Here is the dojo to reproduce. In this dojo I've created imitation of data, that coming from server in our case. The main idea is to have a grid with lazy loading - it has 10 groups (page 1) and after scrolling down it loads 10 more groups (page 2) and etc.
Issue 1.
After scrolling down, data from the last group is updated with some data, that is not belongs to it. Please see 'Issue1.png' attached.
Issue 2.
Groups from the first page are duplicated after scrolling down. For example, there is a group named 'C3'. After scrolling down, it is duplicated once again. Please see 'Issue2.png' attached. New groups are placed after these duplications. By the way, as groups from the 1st page are duplicated, there is more than 20 groups is shown, but the counted at the bottom of the grid says that '20 of 137' elements are show.
So it would be great, if you could fix that. Or even provide temporary fix for us.
Thank you!