Problem:

The DateTimePicker does not work in IE11 due to it's failure to fully support the shorthand syntax for flex (https://github.com/philipwalton/flexbugs#flexbug-4). In order for it to work in IE11 flex-basis needs a unit defined and therefore does not support calc() in this scenario.

Potential Fix:

If you break out flex-grow, flex-shrink and flex-basis then calc() can be used for flex-basis.

Hello support team,

Can you please provide an example in kendo react to upload > crop > save cropped image. My use case is that user should be able to choose, crop and save their profile photo.

Thank you.

The width of the Kendo React DatePicker can become small due to the container width.

In such case, consider the following use case

Users select the date part (year) and start incrementing it by the "up" key. The year date part is selected, but is partially visible,

and the users do not see the date part that they are currently modifying, while they can fully see the other date parts that are not currently in focus.

The DateInput needs a horizontal scrolling to ensure that a focused date part is fully visible to the users in case if the width of the component is narrow.

Please check the case here

https://stackblitz.com/edit/react-8dqy6j-gvgwtk?file=app%2Fmain.jsx 

I noticed that the value prop of the TextAreaChangeEvent is defined as string | number | string[].

When will this value be number or string[]?

Won't it always be string due to the fact that it's a text area input?

Hello,

After taking a look at your example in the documentation here (which doesn't seem to be working) https://www.telerik.com/kendo-react-ui/components/charts/chart/elements/selection/#using-selection-as-navigator 

I fixed the onSelectEnd function and got it working. However, the selection chart is reloading the data every time onSelectEnd changes this.state.min and this.state.max.

Here is the example:

https://stackblitz.com/edit/react-nub1sc?file=app/main.jsx 

As you can see, this makes for a clunky UI.

If this isn't a bug, do you have suggestions on how to fix this?

Thanks,

Orla

The className prop on the ChipList component is ignored in version 3.18.0. A simple addition of class strings does not appear in the compiled product, e.g.

  return (
    <ChipList
      className='flex-layout --wrap --end'
      data={chipData}
      onDataChange={onDataChange}
      chip={props => (
        <Chip removable removeIcon='k-i-close' {...props} />
      )}
    />
  )

I've looked through the transpiled source in node_modules, and it seems the className property passed to the React.createElement() function totally ignores the prop class names.

i am using KendoReact Drawdom version 1.5.12

I have some input elements for uploading images, and showing the a preview of uploaded image.

I want to export a PDF version of the form, but drawDom.cloneNodes() throws an exception when handling input elements of type file. that is because these type of input elements can not have value attribute.

Hello,

I have two Menus and I need to customize their popups differently. Can I specify somehow Menu Popup id or className?

As I can see Popup component has className property, but it is hard-coded in MenuItemInternal.prototype.getPopupClassName and neither Menu nor MenuItem classes are used in popup.

Any suggestions?

Thanks.

DateTimePicker opens above or below the link to open it, however when it's in the middle of a page, it will choose to open below and sometimes require scrolling to see all the buttons.

Would be better, if it were to open offscreen, it should be "pinned" to the bottom edge.  Same for right/left/top borders of the screen.

Certain containers also make it impossible to scroll down to see the buttons, so that creates a real problem. The above proposal would fix this.

using fairly vanilla implementation of the component:

<DateTimePicker
      defaultValue={new Date(ActivationDate.toString())}
      onChange={handleActivationChange}
      width={'8rem'}
 />

Description:

When the NumericTextBox is set to "c0" format and has a value of 0 ($0), it doesn't capture the first digit entered.

Reproduction Steps:

1. Set the field value to 0 ($0)
2. Hit "Tab" to blur the field
3. Hit "Shift-Tab" to focus the field (field contents will be highlighted)
4. Enter "123"
5. Repeat steps 2 through 4

Browser:

Chrome -- Version 89.0.4389.114 (Official Build) (64-bit)

Expected Behavior:

• After step 4, field shows "$123"
• After step 5, field shows "$123"

Observed Behavior:

• After step 4, the field shows "$230"
• After step 5, the field (correctly) shows "$123"

Notes:

• This bug seems to occur when the field has a value of 0 ($0) before gaining focus
• This doesn't occur when the specified format is "c2" or "n0"

Code Snippet:

<NumericTextBox format="c0" />

Description:

When typing into a React autocomplete with the "suggest" prop, the component does not always display the suggestion in the dropdown. It appears that in Chrome, only the very top of the suggestion is visible in the dropdown, while in Edge, it isn't at all.

Reproduction Steps:

1. Navigate to https://www.telerik.com/kendo-react-ui/components/dropdowns/autocomplete/suggestions/
2. Type "d" into the AutoComplete in Uncontrolled Mode example

Browser:

• Chrome -- Version 89.0.4389.114 (Official Build) (64-bit)
• Edge -- Version 89.0.774.68 (Official build) (64-bit)

Expected Behavior:

• The suggestion is fully visible in the dropdown

Observed Behavior:

• The suggestion is either not visible, or only partially visible

Screenshots:

Chrome:

Edge:

Hi,

Currently, we're facing a performance issue in react scheduler, when it has more grouping items(i.e. browser hangs indefinitely). I'm requesting the feature based on the below ticket

https://www.telerik.com/account/support-tickets/view-ticket/1513927

Hi,

I'm using the NumericTextBox to receive a value stored in a state, it has a percent "p3" format so it display numbers like this "0,000 %". When the state change, the value displayed in the NumericTextBox loses its format. If I click in the field and press space or any other key, the format comes back. The expected result was the NumericTextBox always keeping the format, what can be done in this situation?

NumericTextBox code

This is the textbox when I change the value direct in the field, it works fine

The state is shared between 2 NumericTextBox. if I change the value in the other textbox, it loses the format in this textbox

If I go in this textbox and just hit space, the format comes back

What can be done to keep the textbox format?

Thank you

Defined a date rang. But it allows to enter a date larger than a max date of the range. Both via calendar and manually.

const minDate = new Date(1, 1, 1);
const maxDate = new Date(9999, 12, 31);

          return (
           
              <DatePicker value = {this.state.value}
                 
                  min={minDate}
                  max={maxDate}
                
              /> 
           

We have database constraints on certain fields e.g. varchar(10) and would like to prevent the user from entering invalid data into the combo box fields. If it's not too much trouble a minLength field would also be convenient.

The SCSS files from the kendo-theme-material contain !important rule, that makes it difficult to override the styles in the consuming application.

We have a requirement to customize the DatePicker Kendo React component so that it has a border around all 4 sizes, as by default the theme has the border only on the bottom.

We have applied a new custom style to k-picker-wrap  and added the 
border-top-color: $datetime-border !important;

style

But due to the !import rule in the file 

@progress\kendo-theme-material\scss\datetime\_layout.scss, line 15

the custom style that we applied in the consuming application does not get applied.

Please find screenshots with the details of the problem.

The screenshots indicate that the custom style for the border-top-color did not get overriden, and the box is missing the top border.

Kindly advise approach that we can use to customize the CSS styles that has !important CSS rule, so that we can override the styles defined in the material theme.