Reproduction:

1. Open https://demos.telerik.com/kendo-ui/gantt/pdf-export
2. Click "Export to PDF" and open file
3. Actual result: there's a lot of blank space on the right
4. Expected result: the margin should correspond to the pdf.margin.right option
   

On https://demos.telerik.com/kendo-ui?_ga=2.149841974.1082962146.1579102350-1080570292.1579102350 , all links in the "Sample Applications" section return 404 (for example https://demos.telerik.com/bootstrap/ )

Removing all URL params helps.

Any URL param ( https://demos.telerik.com/kendo-ui?x=1 ) reproduces the issue.

Your demo site is broken.

https://demos.telerik.com/kendo-ui/multicolumncombobox/index

Hi Team,

Sorry for the confusion. I don't know where to post this content issue I saw in your website.

Have a nice day :)

Bug report

The workbook exporting to Excel generates a corrupted file when the name of some of its sheets contains a "cell-related" value - for example, "A1", "G5", "F45", etc.

Reproduction of the problem

1. Open this Dojo project and run it
2. Save the exported Excel file and open it.

Current behavior

When the saved file is opened in Excel, a "corrupted file" warning appears on the screen.

Expected/desired behavior

There shouldn't be any warnings when opening a saved workbook

Environment

• Kendo UI version: 2019.3.1023
• jQuery version: x.y
• Browser: [all]

See dojo at https://dojo.telerik.com/@GaloisGirl/akAlaDIP .

The first DateTimePicker is set as readonly and has also aria-readonly manually set to true. It is correctly read by my screen reader (NVDA).

The second DateTimePicker is only set as readonly. It is read by the screen reader editable. It is not marked as readonly in the accessibility tree (per Firefox Developer Edition 71).

I can't find a formal specification, but this page says an input with ARIA role="combobox" needs to have "aria-readonly" set in addition to "readonly".

I'm documenting this for the DateTimePicker , but the same problem occurs for ComboBox ( https://dojo.telerik.com/@GaloisGirl/egeLOxIt ) and possibly other widgets that use the ARIA role combobox.

Hi,

I'm not sure this will be a bug in your mind but I just wanted to make sure I understood how things work. We have a grid definition which includes the dataSource.schema.model definition. One of the fields (TradeDate) in the schema has a type = "date". In addition, we assign local json data to the "data" property of the dataSource. Our JSON data comes in with dates in the ISO format (a string with the "T" in it). When the grid is initially created everything works fine. We notice that the TradeDate field in the dataSource.data() is converted to an actual javascript date. I assume this is happening because of the schema definition. Later we retrieve new data via an ajax call and apply it to the grid using the grid.dataSource.data(newJson) command. However this does not seem to process the TradeDate field and convert it into a real javascript date. This causes problems because we have filters applied based on the TradeDate. It works fine the first time but fails any time the data is refreshed (because the field value is a string). We tried the schema.parse function but that also is only called the first time. Ultimately we coded the grids "dataBound" event and everything worked. It gets called each time the data is refreshed. I was just wondering if I could be doing something differently so that the schema handled the conversion all the time.

self._grid = grd$.kendoGrid({
columns: [...],
        dataSource: {
schema: {
                        model: {
                            id: "somekey",
                            fields: {
                                NewTradeFlag: { editable: false },
                                TradeDate: { editable: false, type: "date" },
...
                            }
                        }
                    },
                data: self.ViewModel.DisplayData.TransactionData
         }
...
})

Later on we do this

self._grid.dataSource.data(newJsonData);

P.S. we originally were using MVVM binding straight to the ViewModel but that didn't work either.

Thank you in advance, Jim.

Bug report

When a custom class attribute is set via the columns.attributes option, the TreeList renders an additional class that is undefined.

Reproduction of the problem

1. Initialize a TreeList.

2. Set a custom class via the attributes option:

3. Inspect the relevant "td" element

Dojo sample for reproduction:

https://dojo.telerik.com/IqApoGOz

Expected/desired behavior

The TreeList should render only the specified classes.

Environment

* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [all] 

The following typings are missing in @types/kendo-ui version 2019.3.0

1. kendo.data.TreeListModel has no parentIdField
2. kendo.ooxml.WorkbookSheetRow has no property "type"
3. kendo.ui.PanelBar has no dataSource
4. kendo.ui.DatePicker has no dateView (it's used in https://docs.telerik.com/kendo-ui/knowledge-base/datepicker-show-quarterly-frequency  )
5. kendo.ui.EditorEvent has no keyCode
6. kendo doesn't expose kendo.wheelDeltaY()
7. kendo.data doesn't expose "binders" (filed at https://github.com/telerik/kendo-ui-core/issues/4049 )
   

dojo: http://dojo.telerik.com/UMuRaBax/3

Steps to reproduce:

1. Run the dojo, let the comobox list load and let it select the default item ('Oulu' in this case).

2. start typing 'Madrid' in the input field of the combobox.

3. press Tab key and observe behavior.

Bug report

Reproduction of the problem

Dojo example.

Current behavior

The mobile material theme does not apply specific styles to a button that has the "km-primary" class. Compare to the Nova mobile theme, which does have specific rules that use ".km-primary" selector.

Expected/desired behavior

CSS rules that use the ".km-primary" selector should be added to the theme.

Environment

• Kendo UI version: 2019.2.619
• jQuery version: x.y
• Browser: [all]

When using a grid with locked columns if the unlocked area is scrollable once scrolled horizontally the resize handle keeps it's original absolute positioning and doesn't respect the change in scroll. 

When hovering over the edge of the column I can no longer see the resize handle. I can hover to the left where it would have been with no scrolling and then see it. 

On DOM inspection I see the event to update the handle's position STILL FIRES when hovering the edge of a column header, but the position is based on scrollLeft() === 0. 

I will assume the needed left position for each column is calculated on creation but is not re-calculated for horizontal scroll. 

This can be reproduced in the live demos on Telerik's site. 

https://demos.telerik.com/kendo-ui/grid/frozen-columns

1 - when use bootstrap v4  theme, ddl does not handle long names gracefully, please find in attachment example in bootstrap v4 & silver themes, also here are the dojo exaples

v4: https://dojo.telerik.com/AYoXEyoT/5

silver: https://dojo.telerik.com/aqIkUSiP/2

2 - for grid and separate controls validation message has diff view

https://dojo.telerik.com/aBuKaDun/6

should be the same

I am currently experiencing an issue between the Kendo ContextMenu and the Kendo EditorFor. When I open the ContextMenu inside of the EditorFor it display offset relative to the cursor, both the left and top values are completely incorrect relative to the editor.

Attached you will find a solution where this issue has been replicated, I removed the scripts folder in order to keep the file size small. I hope this can be fixed soon.

Dear staff,

I am working extensively with Kendo UI Drawing API, specifically with drawDOM and exportPDF methods. I encountered a strange issue, which leads to the generation of corrupt PDF files.

After several attempts to analyze the problem, I found a small piece of code that allows to systematically reproduce the issue. You can find the code as attached.

Opening the example page with Chrome browser I got a corrupted PDF file, while Internet Explorer seems to generate a valid PDF file starting from the same source page.

Checking with an online PDF validator, the file generated by Chrome exploits this validation error:

    “The content stream contains an invalid operator.

      The operator has an invalid number of operands.”

I’m not skilled with PDF internals, but comparing the valid file of IE and the invalid file of Chrome, I noticed that an “infinite” value appears in the invalid PDF.

The row in the valid PDF is “1 0 0 -1 -9494.7900391 -9965.5996094 cm“, while the same row in the invalid PDF is “1 0 0 -1 Infinity Infinity cm”.

I noticed that the presence of an “Infinite” value is the common behavior whenever the corrupt PDF problem occurs.

Reproduction steps:

1. Open column menu

2. Using arrow keys, go to Filter menu item.

3. Hit right arrow to open Filter submenu

4. Tab through filter submenu

5. Hit escape.

Expected behaviour: Filter submenu closes and focus returns to the parent column menu

Actual behaviour: Both filter and column menu are closed.

Snippet: http://dojo.telerik.com/@gearoidj/iqiwUCEp

This is an issue for accessibility users - there doesn't seem to be a way to return to the parent filter menu using the keyboard without closing all menus and reopening them.

There is one way for it to occur, and that is to use the mouse to place the focus on the Filter menu background - in this case hitting escape will close the Filter menu and focus will be returned to the parent column menu. However this is impractical for an accessibility user who is relying solely on keyboard navigation.

An example of where this (mostly) works is on the Columns submenu - the user can use the left arrow key or Escape to close the child menu or alternatively keep tabbing and they will eventually return to the parent menu (though if they do tab within the child menu, hitting Escape will close both the child and parent menus).

Bug report

An error occurs on components' initialization when using a custom Kendo UI build which includes PDFviewer

Reproduction of the problem

1. Go to Kendo UI Custom Download page
2. In the "WEB" section select random components including the Grid and PDFviewer
3. Download the custom build(kendo.custom.min.js file) and put it in the same folder with an HTML file with the following structure.

<!DOCTYPE html>
<html>

<head>
    <style>
        html {
            font-size: 14px;
            font-family: Arial, Helvetica, sans-serif;
        }
    </style>
    <title></title>
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.2.514/styles/kendo.default-v2.min.css" />

    <script src="https://kendo.cdn.telerik.com/2019.2.514/js/jquery.min.js"></script>
    <script src="./kendo.custom.min.js"></script>
</head>

<body>
    <div id="example">
        <div id="grid"></div>
        <script>
            $(document).ready(function () {
                $("#grid").kendoGrid({
                    dataSource: {
                        type: "odata",
                        transport: {
                            read: "https://demos.telerik.com/kendo-ui/service/Northwind.svc/Customers"
                        },
                        pageSize: 20
                    },
                    height: 550,
                    groupable: true,
                    sortable: true,
                    pageable: {
                        refresh: true,
                        pageSizes: true,
                        buttonCount: 5
                    },
                    columns: [{
                        template: "<div class='customer-name'>#: ContactName #</div>",
                        field: "ContactName",
                        title: "Contact Name",
                        width: 240
                    }, {
                        field: "ContactTitle",
                        title: "Contact Title"
                    }, {
                        field: "CompanyName",
                        title: "Company Name"
                    }, {
                        field: "Country",
                        width: 150
                    }]
                });
            });
        </script>
    </div>
</body>
</html>

4. The following error appears:
   Uncaught TypeError: Cannot read property 'Toolbar' of undefined

Current behavior

Expected/desired behavior

A Grid should be initialized properly and without errors if a custom build is including the PDFviewer

Environment

• Kendo UI version: 2019.2.514
• jQuery version: x.y
• Browser: [all]

When a text with background color set is made bold and copy/pasted, the background color is not being preserved.

The issue can be reproduced on the following Dojo example.

Steps to reproduce:

• Type some text.
• Select the text and set a background color.
• Make the text bold.
• Copy/paste the text on a new line.

Bug report

Reproduction of the problem

Dojo example.

Current behavior

A difference between kendo.culture.ar.min.js:

pattern: ["-n %","n %"],

and other Arabic cultures, e.g. kendo.culture.ar-AE.min.js:

pattern: ["-n%","n%"],

A space is present in between the % symbol and the number and the position of the percent symbol differs.

Expected/desired behavior

Format consistency.

Environment

• Kendo UI version: 2019.2.619
• jQuery version: x.y
• Browser: [all]