But when a value is minus it allows decimals.
Hi.
I make kendo grid which has pageable: {pageSizes: true, pageSize: 10} options.
After $("#grid").data("kendoGrid").setDataSource(dataSource), pageSize is changed NaN.
even setOptions() is not working.
$("#grid").data("kendoGrid").setOptions({
pageable: {
pageSizes: true,
pageSize: 10,
}
});
This is sample code.
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<title>Kendo UI Snippet</title>
<link rel="stylesheet" href="https://kendo.cdn.telerik.com/2020.2.617/styles/kendo.default-v2.min.css"/>
<script src="https://code.jquery.com/jquery-1.12.4.min.js"></script>
<script src="https://kendo.cdn.telerik.com/2020.2.617/js/kendo.all.min.js"></script>
</head>
<body>
<div id="grid"></div>
<script>
let dataSource =new kendo.data.DataSource({data:[{ productName: "Tea", category: "Beverages" }]});
$("#grid").kendoGrid({
columns: [
{ field: "productName" },
{ field: "category" }
],
dataSource: [
{ productName: "Tea", category: "Beverages" },
{ productName: "Coffee", category: "Beverages" },
{ productName: "Ham", category: "Food" },
{ productName: "Bread", category: "Food" }
],
pageable: {
pageSizes: true,
pageSize: 10,
},
});
$("#grid").data("kendoGrid").setDataSource(dataSource);
$("#grid").data("kendoGrid").setOptions({
pageable: {
pageSizes: true,
pageSize: 10,
}
});
</script>
</body>
</html>
Bug report
There is no definition of type in the WorkbookSheetRow definition (line 21897 in kendo.all.d.ts):
interface WorkbookSheetRow {
cells?: WorkbookSheetRowCell[];
index?: number;
height?: number;
}
The values of the sheets.rows.type: https://docs.telerik.com/kendo-ui/api/javascript/ooxml/workbook/configuration/sheets.rows.type
Reproduction of the problem
Current behavior
Expected/desired behavior
Environment
- Kendo UI version: 2020.3.915
- jQuery version: x.y
- Browser: [all]
Bug report
The kendo.culture.nb-NO.min.js file contains some unwanted characters: "Â".
Reproduction of the problem
See Ticket ID: 1486493 for more details.
The unminified file looks correctly: https://github.com/telerik/kendo-ui-core/blob/master/src/cultures/kendo.culture.nb-NO.js
Current behavior
Expected/desired behavior
Environment
- Kendo UI version: 2020.3.915
- jQuery version: x.y
- Browser: [all]
Prerequisites: Chrome browser, Outlook 2016 or 365
Steps to Replicate
From Outlook, click to hold down on an email. Drag and drop it to the upload area.
Expected Behavior: The e-mail is copied to the upload widget and uploaded.
Actual Behavior: E-mail is deleted from the folder it existed in and moved to "Deleted Items". If it was copied from "Deleted Items", it is permanently deleted.
Notes:
This does not work in Firefox or Safari--it appears a new version of Chrome enabled the "drag-and-drop from emails" feature. Drag and drop from the other two browsers simply does nothing.
There is already technology to provide a "copy" option for drag-and-drop implementations from emails. (https://answers.microsoft.com/en-us/msoffice/forum/all/drag-and-drop-works-however-deletes-email-can-we/865f60c3-7980-4465-8a19-4d60b0ae5aba?page=2)
Telerik has stated that they "do not support" this feature (source: https://www.telerik.com/forums/drag-and-drop-outlook-email) I would like this feature to be supported.
1. Create a table
2. Add a caption
3. Select caption and format it to be a heading (h1, h2..)
4. Note that the layout becomes distorted.
It is expected that the heading element will be wrapped in the caption element, which is valid html5 according to w3 validator
http://validator.w3.org/#validate_by_input
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document</title>
</head>
<body>
<table style="width:1177px;"><caption><h2>Text</h2></caption><tbody><tr style="height:21px;"><td style="width:382.812px;">a</td>
<td style="width:382.812px;">a</td>
<td style="width:381.812px;">a</td>
</tr>
<tr style="height:21px;"><td style="width:382.812px;">a</td>
<td style="width:382.812px;">a</td>
<td style="width:381.812px;">a</td>
</tr>
</tbody></table>
<p> </p>
</body>
</html>
This behaviour has already been discussed with Yanko Dzhemerenov internally.
There is an issue with LESS Fiori Theme on the Last release of Kendo UI Scheduler. The issue can be observed in the demos:
I'm trying to use the workDays option to only show Saturday and Sunday in the workWeek view (this is for a weekend working rota -- I don't want to show Mon - Fri):
{ type: "workWeek", selected: true, workDays: [6,0] },However, only Saturday is being displayed.
Note, I'm using a custom culture that sets the first day of the week to Saturday, but the same problem occurs when using the standard en-GB culture.
Bug report
Horizontal and vertical lines appear in the merged Spreadsheet cells when they are disabled.
** Possible workaround could be to apply the following CSS:
#spreadsheet > div.k-spreadsheet-view > div.k-spreadsheet-fixed-container > div.k-spreadsheet-pane > div.k-spreadsheet-data > div.k-state-disabled {
opacity: 1;
color: #a3a3a3;
}
Reproduction of the problem
- Open this Dojo and run it
- There are is a horizontal line above the cell with text "Merged DISABLED cell and there is a horizontal line above". There is a vertical line inside the cell with text "Two cells are merged horizontally and the result cell is disabled. There is a vertical line that should not appear"
Current behavior
When Spreadsheet cells are merged and the result cell is disabled, there are horizontal or vertical lines that appear inside the merged cell.
Expected/desired behavior
No lines should appear inside the merged cells, no matter if they are enabled or disabled.
Environment
- Kendo UI version: 2020.3.1021
- jQuery version: x.y
- Browser: [all]
Hi Keno Team,
I am getting this CORS error when trying to open a pdf file from an Azure blob using kendoPDFViewer. (Error: ' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. )
I have an SSL token included to pdf/image URLs and work fine for image viewing with kendoImageEditor.
My code is simple as follows
this.viewer = $("#pdfViewer").kendoPDFViewer({
pdfjsProcessing: {
file: pdfUrl,
},
width: "100%",
}).data("kendoPDFViewer");
Could you please let me know how to fix this issue
Hi Kendo Team,
I am getting this error when trying to open a pdf from Azure Blob using kendoPDFViewer. (Error: has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.)
I use token-based authentication by SSL token included to the image/pdf URLs and It works fine for image viewing using kendoImageEditor.
My code is simple as follows:
this.viewer = $("#pdfViewer").kendoPDFViewer({
pdfjsProcessing: {
file: pdfUrl,
},
width: "100%",
}).data("kendoPDFViewer");
Could you please let me know how to fix this issue?
Or do I need to use dplProcessing with an Authorization token
Bug report
Reproduction of the problem
Dojo example.
- Click the "export" button
Current behavior
Drawing does not export the content. This is due to the img tags having a loading="lazy" attribute.
Expected/desired behavior
The images are exported. The attribute should be stripped if needed.
Environment
- Kendo UI version: 2020.3.1021
- jQuery version: x.y
- Browser: [Chrome XX | Firefox XX ]
Bug report
Reproduction of the problem
Dojo example.
Current behavior
Data is exported incorrectly.
Expected/desired behavior
Data is exported correctly (see the Spreadsheet export)
Environment
- Kendo UI version: 2020.3.1021
- jQuery version: x.y
- Browser: [all]
Hello, there is a comment in the Resize API demo example for popup modal windows that is opposite the way it actually works, right?
resize - API Reference - Kendo UI Window | Kendo UI for jQuery (telerik.com)
i.e. the user has STARTED resizing the window
Hi all,
I would like to request a feature by enabling sorting of grouped headers only by the sum of values in a specified column.
Thank you.
Hi,
I've notice an issue with Scheduler: the height for group slot is not correct calculated and items goes down to the next group slot.
Scheduler :
- group vertical after a field
- type of scheduler: "timelineWeek" or "timelineMonth"
- items of the group have same start date and their number are bigger then 20.
kendo ui version: 2020.1.219. Same issue with 2021.1.119
----------------------------------------------------------------------------------------------------------------------
I've created a dojo as example: https://dojo.telerik.com/EHeNigIQ . Also, you can see the issue into the picture bellow.
You can modify the variable "rows = 30;" and you will see more items that goes wrong into the other group slot.
Hi Neli, I have an even bigger problem. Could you tell me how to configure the "enter" to be a "<br>" and not a "<p>". I am having a lot of problems. In the editor I press enter but since a <p> is inserted, my report shows it all together, without line breaks. I need an urgent answer please.
Attached images of the insertion problem of <p>
Thanks
This is somewhat related to the existing request for this feature with Tooltips, but applies more generally to any widgets with popup behavior, such as DropDownList and AutoComplete. Auto-closing these widgets upon scrolling is an extremely annoying behavior, and I've even had end users comment on it in demos. The currently suggested workaround is hacky, particularly difficult to implement with AngularJS, and as far as I know, only works with DropDownList and AutoComplete. This behavior needs first-class support as a configurable option. This could be done a couple of ways.
1. Make it a configuration option.
$("#products").kendoAutoComplete({ closeOnScroll: false });2. Or, just add the browser-level event name to Kendo UI's event object in the various widget event handler functions, such as close.
close: function (e) {
// won't work because "e" doesn't have a "type" property like normal JavaScript event objects do
if (e.type === "wheel") {
e.preventDefault();
}
}
I would actually prefer the second option, as it would open up a bunch of options for developers in those event handlers, including addressing this particular auto-closing issue.