I'm submitting a...

• Suggestion for improvement

Current behavior

When the grid data source is empty, the grid is "just" emtpy

Expected behavior

I didn't find a way to easily set a "no data" text that would be displayed when the grid datasource is empty

Minimal reproduction of the problem with instructions

Set up a Kendo React Grid, with an empty data source

What is the motivation or use case for changing the behavior?

I would like to be able to let the user know that the grid is functionning correctly, and that their search simply didn't come up with any results.

Environment

Latest kendo grid version

Currently, the format property of the column is applied only to the read-only data inside the cell.
Based on the following ticket: 1174726 there is a proposal the format property to be passed down the editor as well.

The current approach is making a custom cell and modifying the editor directly as shown here: https://stackblitz.com/edit/react-dwndnu?file=index.js

I'm submitting a...

• Bug report

Current behavior

Resizable toggle, after the table rendering doesnt work.
Active -> Deactive works.
Deactive -> Active doesnt work. The handle is shown, but not draggable.

Expected behavior

After setting resizeable = true -> columns are resizeable

Minimal reproduction of the problem with instructions

i attached a small sample Site

What is the motivation or use case for changing the behavior?

we tried a workaround for another issue and found this by accident. :)

Environment

0.5.0

Browser:

• Firefox

Sample
kendoReactTest.zip

open console and run
npm install
npm run dev

I'm submitting a...

• Bug report

Current behavior

Create a table, resize a column - sidescrolling activates, and select in "Unit Price" e.g. "less than"

Changing the operator, without having any filter value triggers the filter, the result is empty and the scrollbar disapears. The user cant even reset oder change the filter in this case.

Expected behavior

We have 2 Issues.

• filtering should not trigger if there is no value.
• even in a table without rows, only displaying the table header, scrolling has to be possible

Environment

Package versions: 1
Browser: Firefox

I'm submitting a...

• Bug report

Current behavior

The Grid wrapper filterMenuOpen event is not fired.

Expected behavior

The event is fired in the jQuery version.

Minimal reproduction of the problem with instructions

This can be observed in the following example: https://plnkr.co/edit/gLYYUOI93nr0FDm7959A?p=preview

Environment

Package versions:

Browser:
All
System:

I'm submitting a...

• Bug report

Current behavior

Currently, the DropDownList fails to render the textField correctly when initially setting the value of said DropDownList from componentDidMount. It does however correctly reflect the change of value from the componentDidMount.

Side note: The data is an array of objects that look like

{
    id: number;
    title: string;
    value: string;
}

Expected behavior

The DropDownList should render the textField properly when setting an initial value outside of the onChange function. This would be a controlled DropDownList.

Minimal reproduction of the problem with instructions

I have created a codesandbox demo perfectly recreating this bug. You can take a look at the console to see the current state. I have created the initial value to be the same as the first option in the dropdown list which is Animals.

Codesandbox: https://codesandbox.io/s/5wm4rp6orp
Codesandbox Standalone: https://5wm4rp6orp.codesandbox.io/

Steps to take:

1. Load demo
2. Observe the current state after componentDidMount
3. Select Animals
4. Observe the new state
5. textField correctly renders only after selecting the same value

What is the motivation or use case for changing the behavior?

The states between mounting and selecting the same option are exactly the same. However, what is not the same is the failure to render the textField even though the "different" states are exactly the same.

Environment

Package versions:

+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY cldr-data@^32.0.0
+-- [email protected]
+-- UNMET PEER DEPENDENCY [email protected] - 3
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY react-scripts@^1.0.14
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

Browser:

• Chrome (desktop) version 67.0.3396.99
• Chrome (Android) version 67.0.3396.87
• Firefox version 60.0.2
• IE version 11.2363.14393.0
• Edge version 38.14393.2068.0

System:

• TypeScript version: 2.9.1
• Node version: 8.9.3
• npm version: 5.5.1
• Platform: Windows

Can somebody tell me, whats inside of Version 1.0.1?

The Changelog on the official homepage ends with Version 1.0.0. Or is there another place to find the updated changelogs?

I'm submitting a

• Bug report

Current behavior

progress/kendo-react-dropdowns 0.3.0.
When multiple DropDownList components with filtering are on the same page, clicking on next dropdownlist with in a second causes an un-handled error "TypeError: _this._element is undefined"
I think it is happening if the second dropdown is clicked while the close animation of the first one is not yet complete.
TypeError: _this._element is undefined

Popup/_this.onClosing
Popup.js:77
<anonymous> self-hosted:950:17 onExiting
AnimationChild.js:93
CSSTransition/_this.onExiting
CSSTransition.js:252
performExit/<
Transition.js:273
setNextCallback/this.nextCallback
Transition.js:318
safeSetState/<
Transition.js:304
commitCallbacks
react-dom.development.js:6163
commitLifeCycles
react-dom.development.js:8784
commitAllLifeCycles
react-dom.development.js:9946
callCallback
react-dom.development.js:542
invokeGuardedCallbackDev
react-dom.development.js:581
invokeGuardedCallback
react-dom.development.js:438
commitRoot
react-dom.development.js:10050
performWorkOnRoot
react-dom.development.js:11017
performWork
react-dom.development.js:10967
requestWork
react-dom.development.js:10878
scheduleWorkImpl
react-dom.development.js:10732
scheduleWork
react-dom.development.js:10689
enqueueSetState
react-dom.development.js:6212
./node_modules/react/cjs/react.development.js/Component.prototype.setState
react.development.js:237
safeSetState
Transition.js:302
performExit/</<
Transition.js:276
setNextCallback/this.nextCallback

Expected behavior

Clicking on dropdownlist to see options should work without error when there is multiple dropdownlist components on screen.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/VQCFGtAXKbLeaqjriKLq?p=preview

What is the motivation or use case for changing the behavior?

No change in behaviour - fix the error.

Environment

React 16.
Package versions:
progress/kendo-data-query: 1.2.0,
progress/kendo-react-dropdowns": 0.3.0,
progress/kendo-react-layout: 0.3.0,
progress/kendo-ui: 2018.1.117,

Browser:
<!-- Leave only the browsers that you tested the issue with. -->
- Chrome (desktop) Version 64.0.3282.167 (Official Build) (64-bit)
- Firefox version 58.0.1 (64-bit)

System:
- Node version: v6.11.5, npm: 3.10.10
- Platform:  Windows

<!-- Add any additional information that might be relevant. -->

I'm submitting a...

• Bug report
• Documentation issue or request

Current behavior

When you add the "export to Excel" feature to the kendo grid toolbar, it does not work. The button appears as "Export to Excel" with the parameter "excel" however the button does not do anything.
It works in JQueary.

Expected behavior

It is supposed to export the data to an excel file.

Minimal reproduction of the problem with instructions

Just add a toolbar to a grid with the parameter "excel" passed in. I am using react wrapper

https://plnkr.co/edit/hYuYDO9KCFHPUgWCdZJY?p=preview

What is the motivation or use case for changing the behavior?

It is a feature that is advertised and yet is not supported by one platform.

Environment

Package versions:

+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

Browser:

• Chrome (desktop) version 67.0.3396.99 (Official Build) (64-bit)

System:

• TypeScript version: 2.9.2
• Node version:10.0.0
• NPM version: 6.1.0
• Platform: Windows

• Bug report

Current behavior

Using the Kendo Dropdownlist React Wrapper 2018.1.221 when the a page is scrolled and the dropdown is selected the list of items is detached from the heading and is displayed further down the page. I have the same issue fixed on other libraries (Angular, JQuery).

Expected behavior

Body of list should appear under heading

Minimal reproduction of the problem with instructions

My code is pretty striaght forward. It is like:

render() {		
		return (			
			<div className="form-group row" id={this.props.fieldName}>
				<label className="col-sm-4 col-form-label">{this.title}</label>
				<div className="col-sm-8">
					<DropDownList
						placeholder={this.placeholder}
						select={this.onChange}
						value={this.props.value}
						dataSource={this.props.lookupData}
						dataTextField={this.textField}
						dataValueField={this.valueField} />
				</div>
			</div>
		);		

What is the motivation or use case for changing the behavior?

Environment

Browser:

• Chrome (desktop) version Latest
• Firefox version Latest
• IE version 11

It would be great if we add an option to customize the Grid filter more.
For the moment the filter look like this :

It would be very helpful if we can change the layout of filtering for example this way :

I'm submitting a...

• Feature requests

Current behavior

The resizing Event is triggered multiple times.

Expected behavior

We would like to have some columnResized-event / columnResizeEnd-Event. Similar to columnResize-event, but it should only to be triggered once at the end of the resize process (Handle drop). The current implementation of columnResize-event triggers multiple times during the actual resize process.

I'm submitting a...

• Bug report

Current behavior

Browser throws warning messages,
(Emitted value instead of an instance of Error) Cannot find source file '../../../src/barcode/index.tsx': Error: Can't resolve '../../../src/barcode/index.tsx' in '<app-path>\node_modules\@progress\kendo-barcodes-react-wrapper\dist\es\barcode'

Expected behavior

No warning messages should be thrown.

Minimal reproduction of the problem with instructions

Run the application in dev mode with warnings enabled.

What is the motivation or use case for changing the behavior?

We flag warning messages in build log, this contributes to large amount of warnings.

Environment

Package versions:

"@progress/kendo-barcodes-react-wrapper": "^2018.1.221",
    "@progress/kendo-react-buttons": "^0.5.1",
    "@progress/kendo-react-common": "^0.5.1",
    "@progress/kendo-react-ripple": "^0.5.1",
    "@progress/kendo-theme-default": "^2.51.0",
    "@progress/kendo-ui": "^2018.1.503",
    "@progress/kendo-window-react-wrapper": "^2018.1.221",

Browser:

• Chrome (desktop) version XX

System:

• TypeScript version: 2.8.1
• Node version: 8.9.1
• Platform: Windows

I'm submitting a...

Bug report

Current behavior

Currently crashes with an error document is not defined, looks like the document.body usage.

Expected behavior

Render successfully

Minimal reproduction of the problem with instructions

Using https://github.com/aspnet/JavaScriptServices to prerender pages, not reproducible in PLUNKER.

What is the motivation or use case for changing the behavior?

Faster initial page rendering

Environment

Package versions:

├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Browser:

• Chrome (desktop) version 65.0.3325.181

System:

• TypeScript version: 2.7.1
• Node version: 8.9.4 (NPM 5.7.1)
• Platform: Mac

Currently, the DropDowns can be bound only to flat data.

There are cases where the desired text or value field could be placed inside a complex object field.

We should consider making an enhancement to support binding to a complex data object as well.

I'm submitting a...

• Suggestion for improvement

Current behavior

When settting a GridColumn "cell" attribute, just like the example in https://www.telerik.com/kendo-react-ui/components/grid/
it overrides the "editor" attribute
I'd like to be able to set a cell template for a column representing a boolean field, that doesn't just contain "true/false"

Expected behavior

If possible, the editor attribute should have priority on the "cell" one, or perhaps it would be easier if we could set a "displayCell" independantly

Minimal reproduction of the problem with instructions

Set up a grid, add a GridColumn linked to a boolean field

I'm submitting a...

• Bug report

Current behavior

• The necessary data for the columns are part of an object inside the state of the component that use the kendo react grid
• Update the Width Property of the Column does not trigger a rerender of the table
• Make a resize of a column trigger the rerender of this column with the new width

Expected behavior

• After updating the width of a column, rerender the column with this new width
• with version 0.3 it works

What is the motivation or use case for changing the behavior?

We used the kendo react solution for tables with many columns and not much space for the filter row. so we decided to add a minimal width to the table columns, when filter row is activated. We have build a toggle Button to activate/deactivate the filter row and with this button we also want to change the minimal width of the columns.

Environment

Package versions:

@progress/[email protected]

Browser:

• Firefox version 52.1

System:

• TypeScript version: 2.3
• Node version: 6.11.1
• Platform: Windows

I'm submitting a...

• Bug report

Current behavior

Currently the width is only "updatable" if resizable is deactivated

Expected behavior

We need to set/update the Column.Width at any time. Even if resizable is active.
This should only trigger when the new value is different from the last value. Otherwise we would override the resized width every time.

Minimal reproduction of the problem with instructions

i attached a small sample Site

What is the motivation or use case for changing the behavior?

We need to update the columns width after specific user input.

Environment

0.5.0

Browser:

• Firefox

Sample
kendoReactTest.zip

open console and run
npm install
npm run dev

Current behavior

• The react grid onPageChangeEvent is not firing when using virtual scroll and the page is scrolled to its limit.

Expected behavior

The react grid onPageChangeEvent is not firing when using virtual scroll and the page is scrolled to its limit.

Minimal reproduction of the problem with instructions

• I cannot reproduce this in plunker https://plnkr.co/edit/dWc90J?p=preview but locally when I npm install kendo react grid using the virtual scroll example code.

Environment

Package versions:

├── @babel/[email protected]
├── @material-ui/[email protected]
├── @material-ui/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── @progress/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Browser:

• All

System:

• All

I'm submitting a

• Bug report

Current behavior

Combobox will not lose focus when the suggestion option is set.

Minimal reproduction of the problem with instructions

The issue can be observed in the demo https://www.telerik.com/kendo-react-ui/components/dropdowns/combobox/suggestions/

Click in the input and then click on the search bar:

Environment

Browser:

• IE version 11

Currently there are only 5 options for the filter cells: text, boolean, numeric, date and disabled filtering for the column.

The user should be able to customize the filter cells similar to how he can define custom Cells for the data rows.

Possible solutions:

• render prop for the component used in the filter cell
• custom filter component for inside the filter cell
• filterCell prop for the whole cell
• render prop for the whole cell

I'm submitting a...

• Bug report

Current behavior

DropDownList menu is behind the Dialog

Expected behavior

It should be above the Dialog and not covered by the Dialog

Minimal reproduction of the problem with instructions

https://next.plnkr.co/edit/OY5VngU7Gb6ASF89

The property should control the checked value of the header checkbox of the column, that is currently uncontrolled and only fires headerSelectionChange event when changed.

Add demo with Draggable.

The demo should demonstrate how to integrate the kendo-draggable package in React application.

I'm submitting an issue

• Bug report

Current behavior

The DatePicker Calendar is not opended if the component input is focused on IE11

Minimal reproduction of the problem with instructions

The issue can be observed in the demo: https://www.telerik.com/kendo-react-ui/components/dateinputs/datepicker/

Environment

Browser:

• IE version 11

We have two main options for rendering column aggregates.

1. Having a footer cell where the aggregates will be rendered.
2. Having frozen rows and using one of the frozen rows to display the aggregates.

CC @telerik/kendo-react-team please share your ideas.

The default property of the DropDown is not changed dynamically.

https://next.plnkr.co/edit/1yB8JQSjGfVlZ0RU

In this demo: https://www.telerik.com/kendo-react-ui/components/inputs/numerictextbox/formats/

• Deleting the percentage sign results in 100%.
• The user is not able to delete the first digit

I'm submitting a bug report on React Scheduler wrapper

• Bug report
  kendo.ui.Scheduler

Current behavior

While using "change" Event on kendo.ui.Scheduler when this.destroy() function is called the toolbar on the top still persists (see in https://dojo.telerik.com/UZUsAtuj).
And also in the browser console it shows an error

Uncaught TypeError: Cannot read property 'find' of null
    at init._mouseDownSelection (kendo.all.js:103091)
    at HTMLTableCellElement.<anonymous> (kendo.all.js:103035)
    at HTMLDivElement.dispatch (jquery-1.12.4.min.js:3)
    at HTMLDivElement.r.handle (jquery-1.12.4.min.js:3)

Expected behavior

When this.destroy() is called in "change" Event the whole scheduler component should be removed. And no error like init._mouseDownSelection is expected.

Minimal reproduction of the problem with instructions

https://dojo.telerik.com/UZUsAtuj
Expected solution as per my understanding

__mouseDownSelection event in kendo.all.js has the line of code shown below. Removing this line could be a potential solution.
this.toolbar.find('ul > li').removeClass(FOCUSEDSTATE);

What is the motivation or use case for changing the behavior?

We want to try Kendo Scheduler React wrapper for a project in our organisation.
When I am using "change" Event on the Scheduler React wrapper I want to leave the Scheduler React component and display another component without error and breaking the component.

Environment

Package versions:

   "@progress/kendo-scheduler-react-wrapper": "^2018.2.612",
   "@progress/kendo-theme-default": "^2.53.2",
   "@progress/kendo-ui": "^2018.2.613"

Browser:

• Safari (iOS) version 11.2, 11.4

System:

• Node version: v9.5.0
• npm: 6.1.0

I'm submitting a...

Suggestion for improvement

Current behavior

When using TypeScript to create a component that extends GridCell that is no way that I can see to use your own state properties.

Expected behavior

TypeScript friendly way to create and use your own state in a component that extends GridCell.

Minimal reproduction of the problem with instructions

import { GridCell } from '@progress/kendo-react-grid';
import * as React from 'react';

type State = {
  show: boolean;
}

export class ActionCell extends GridCell<{}, State> {
  public render() {
    return (
      <td>
        Popup here that uses this.state.show
      </td>
    );
  }
}

Possible Solution (GridCell.d.ts)

UPDATE: I realized this won't work as the GridColumn component complains it can't use them.

export default class GridCell<GridCellProps, S = {}> extends React.Component<GridCellProps, S> {
    /**
     * @hidden
     */
    render(): JSX.Element;
}

What is the motivation or use case for changing the behavior?

Environment

Package versions:

+-- @progress/[email protected]

Browser:

• Chrome (desktop) version 65.0.3325.146

System:

• TypeScript version: 2.7.2
• Node version: v8.9.4, v5.7.1
• Platform: Windows

I'm submitting a...

• Bug report

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/2Ea9lePWieN6HRe6nB0h?p=preview

I'm submitting a...

• Bug report

Current behavior

The value to the MultiSelect is not set if the initial value is not part of the initial page size. In the same case in the jQuery widget, the value is selected.

Expected behavior

The value is selected initially.

Minimal reproduction of the problem with instructions

The issue can be observed here:

https://plnkr.co/edit/nxa6yaMlpTLjsa0MdwAR?p=preview

https://dojo.telerik.com/UkaYuyiP

I'm submitting a...

• Suggestion for improvement

Expected behavior

We would like to have more control over the tr for two reasons.

• Attaching additional Event Handler
• Adding CSS Classes

In our case we have an implementation for single click, double click, right click and on top of that shift & strg click zu manage all possible ways of selecting rows. i can attach them to the cells by using custom cells, but is painful to do.
Same for css - sometimes possible by using cumstomcells. Our use case for this, is changing the border on specific table rows - depending on the dataitem - to implement some sort of visual grouping.

I'm submitting a...

• Bug report

Current behavior

The DropDown is returning the nativeEvent and the syntheticEvent as undefined in its change event.

This can be observed in our events demo: https://www.telerik.com/kendo-react-ui-develop/components/dropdowns/dropdownlist/#toc-events

This is causing other components as the Grid which are utilizing the events to break.

Browser:

• All

I'm submitting a...

• Bug report

Current behavior

Scrolling DropDownList items using scrollbar doesn't work in IE11 in kendo-react-dropdowns DropDownList.

Expected behavior

User should be able to use the dropdownlist's scroll bar to scroll through the items in IE11.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/EhrJMld2Zn6skN5ytQS8
This is reproducible on the "Basic Usage" demo code in https://www.telerik.com/kendo-react-ui/components/dropdowns/

1. Click on the dropdown so that the item list pops up,
2. Click on the scrollbar in the item list and try to scroll down
   Expected: item list scrolls
   Actual: the item list popup closes.

What is the motivation or use case for changing the behavior?

It is a bug that affects user experience as it limits user to either use mouse scroll wheel or up and down arrow keys to scroll through list items in IE11.

Environment

Reproducible on the latest demo code at https://www.telerik.com/kendo-react-ui/components/dropdowns/
Package versions:
progress/kendo-data-query: ^1.2.0,
progress/kendo-dateinputs-react-wrapper: ^2018.1.131,
progress/kendo-react-dropdowns: ^0.3.0,
progress/kendo-react-layout: ^0.3.0,
progress/kendo-ui: ^2018.1.117,

Browser:

• IE version 11 (11.0.9600.18893)

System:

• Node version: v6.11.5, 3.10.10(npm)
• Platform: Windows 7 Professional SP1.

I'm submitting a...

• Bug report

Current behavior

The Switch does not slide(only in Material theme)

Minimal reproduction of the problem with instructions

The issue can be observed here: https://next.plnkr.co/edit/0fuYDpHRBKfdr19t

Browser:
-All

I would like a package.json example that works with kendo-react. I have been unable to find the secret combination of versions for the packages that I have installed.

Environment

Package versions:

[email protected] C:\Users\kburton\Projects\cpp\web
+-- [email protected]
+-- [email protected]
+-- UNMET DEPENDENCY [email protected]
| +-- [email protected]
| +-- [email protected]
| `-- [email protected]
+-- UNMET DEPENDENCY [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_module
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_modu
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_modules\
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_mo
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_modu
npm ERR! extraneous: [email protected] C:\Users\kburton\Projects\cpp\web\node_modules\fsevents\node_mo
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]

Browser:

• Chrome (desktop) Version 67.0.3396.99 (Official Build) (64-bit)
  System:
• TypeScript version: 2.0.0 (beta integration with VS 2015)
• Node version: v8.1.3
• Platform: Windows

I'm submitting a...

• Bug report

Current behavior

1. We hold our column configuration array in our component state (state.columns)
2. In render method we render Kendo JSX Element for each column in state.columns
3. On Kendo Grid columnReorder Event we get new Column Order
4. Now we need to update state.columns to reflect the new Column Order. At this Point the Column order is changed again and messed up.

Expected behavior

The column order should not be affected

Minimal reproduction of the problem with instructions

i attached a small sample Site

What is the motivation or use case for changing the behavior?

We need to update state.columns because other Components independent of the kendo grid have to reflect the new order too.

Environment

0.5.0

Browser:

• Firefox

Sample
kendoReactTest.zip

open console and run
npm install
npm run dev

Improve TabStrip performance when switching between taps.

Currently, if the animations are on, the TabStrip content will re-render multiple times.

Also, when we change taps, we are re-instantiating the components inside instead of re-rendering them.

• Bug report

Current behavior

Inputs do not allow spaces, and forms cannot be submitted when pressing enter.

This is caused by the keyboard navigation as it is listening for space and enter keypress events:

case Keys.space: action = NavigationAction.Toggle; break;

case Keys.enter: action = NavigationAction.Toggle; break;

Minimal reproduction of the problem with instructions

The issue can be observed in the following Plunker:

https://plnkr.co/edit/mgd7FRGLjAvWpEULu883?p=preview

Environment

Package versions:
All
Browser:
All

I'm submitting a...

• Bug report

Current behavior

If you use a GridInput in an iframe and get the data from a parent window, the data is not recognized as an Array because of the issue mentioned here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray

The exact error is TypeError: Cannot read property 'length' of undefined (see console output in the reproduction Plunkr)

Expected behavior

Data should be recognized as an Array. Easiest fix for this is to use Array.isArray(data) instead of data instanceof Array

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/dzp5ZOdA0GELTiMu1ct8?p=preview
See the console output for the error and difference of Array.isArray vs. instanceof

What is the motivation or use case for changing the behavior?

We are using GridInputs inside iframes and are running into this issue.

I'm submitting a...

• Regression report
• Bug report
• Suggestion for improvement
• Documentation issue or request

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation or use case for changing the behavior?

Environment

Package versions:

Browser:

• Chrome (desktop) version XX
• Chrome (Android) version XX
• Chrome (iOS) version XX
• Firefox version XX
• Safari (desktop) version XX
• Safari (iOS) version XX
• IE version XX
• Edge version XX

System:

• TypeScript version: XX
• Node version: XX
• Platform:

I'm submitting a...

Bug report

Current behavior

When using a <Grid> component and setting the ScrollMode to none, the <GridToolbar> component doesn't render.

Expected behavior

The <GridToolbar> component should render.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/oSFk7bH9HRkbQkxWnFAe?p=preview

Test button should appear.

Environment

Package versions:

+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @progress/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- @types/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY cldr-data@^32.0.0
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- UNMET PEER DEPENDENCY [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

npm ERR! peer dep missing: react@^15.0.0, required by [email protected]
npm ERR! peer dep missing: cldr-data@^32.0.0, required by @progress/[email protected]
npm ERR! peer dep missing: ajv@^6.0.0, required by [email protected]
npm ERR! peer dep missing: ajv@^6.0.0, required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]
npm ERR! missing: [email protected], required by [email protected]

Browser:

• Chrome (desktop) version 65.0.3325.146

System:

• TypeScript version: 2.7.2
• Node version: v8.9.4, v5.7.1
• Platform: Windows

How to reproduce:
Place DatePicker and NumericTextBox on the same page.
Click on the DatePicker button to open the Calendar.
Click on the spin buttons of the NumericTextBox to increase or decrease value.

Expected: If we open the DatePicker's calendar, clicking anywhere on the page should close it.
Actual: Date picker remain open.

https://plnkr.co/edit/zw5pjVWbUQh6TAKUDAAU?p=preview
Checkbox stays unchecked when clicked, and sorting is applied by default for the column and can't be disabled.

I'm submitting a...

• Bug report

Current behavior

When filtering a Date the options "is before" & "is before or egual to" are switched in their outcome.

Environment

Version 0.5.0

I'm submitting a...

• Bug report

Current behavior

Combo box with value set to a custom value, and allowCustom set to true, doesn't display the custom value unless it is an option in the data source array.

Expected behavior

Display the text even though it's not in the data source.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/wD0zpCTTVSyt41ZF4ndl?p=preview

The 1st combo box should say 'test' as evidenced in app/main.jsx, but only the 2nd combo box with a matching data field shows the value.

What is the motivation or use case for changing the behavior?

We have a 'title' combo box with options like Mr, Miss, etc, but allow users to enter their own custom title. When the file is saved, and then opened for editing, the title field is blank when they entered a custom title.

Environment

Browser:

• Chrome (desktop) Version 67.0.3396.99 (Official Build) (64-bit)

System:

• Node version: v8.9.3
• Platform: Windows

I'm submitting a...

• Bug report

Current behavior

The value of the Grid pager input is not changed when changing the page with the arrows.

Expected behavior

The value has to be changed based on the newly selected page.

Minimal reproduction of the problem with instructions

This can be observed in our demo: https://www.telerik.com/kendo-react-ui/components/grid/paging/#toc-paging

Browser:
All

System:
All

I'm submitting a...

• Enhancement
• Suggestion for improvement

Expected behavior

Allow using the grouping UI for adding, removing and reordering groups without requiring the Grid data to be grouped as well.

Based on the ticket: 1174171