Hi Kendo Angular team,

It will be a good addition to the Kendo UI internalization to add support for the 'j' input skeleton symbol.

https://www.unicode.org/reports/tr35/tr35-dates.html#dfst-hour

Thank you for your consideration.

Dear Support Team,

I had a problem with the Scheduler-Component

So my Problem was that the Resource[] in the Scheduler-Component did not work as an Array. It always used only the first entry.

I tried to create multiple Resources and filled the Array with them, but I only could use the first Entry to style an event.

Because of this "bug" I had to do a huge workaround to colorize multiple different type of events.

When the user enters each character into the combobox, the system should validate that the resulting value is valid. If not, the system should not display the character

Step to produce:

1. Give focus to combobox

2. Type res

3. System should select Residential

4. Type z

5. System should not accept z character (both values in list that start with res do not have a z as the next character)

6. Type t

7. System should select Restaurant

8. Type y

9. Tap Tab

Expected Result: Restaurant should be selected

<kendo-combobox class="kendo-combobox" [ngClass]="{'inactive-color' : custColor}"
         #comboboxComponent [openOnKendoFocus]="comboboxComponent"
          formControlName="CustType" [data]="custTypes" textField="Description" valueField="CustTypeID"
          [suggest]="true" [valuePrimitive]="true" [allowCustom]="false" (selectionChange)="onCusttypechange($event)">
          <ng-template kendoComboBoxItemTemplate let-dataItem>
            <span class="template_lbl" [ngClass]="{'inactive-color' : dataItem.QInactive}">
              {{ dataItem.Description }}</span>
          </ng-template>
        </kendo-combobox>

As a end user I should be capable of assigning my own accessibility attributes. right now I could see that input automatically mapping area-describedby from hint component. 

Please do the needful.

The TextBox component allows us to specify a template for the prefix and suffix areas by applying the TextBoxPrefixTemplate and TextBoxSufffixTemplate directives to an ng-template.

I would also like to able to specify a template for the actual input area itself. 

My use case for this is that I have a directive that I use within my application that I would normally apply to the <input> tag to ensure some custom processing is undertaken during user input. With the current TextBox component I am unable to do this.

Additionally I would like to specify the autocomplete attribute for the <input> tag to alow the browser to autocomplete things such as shipping-address etc. or even to disable the browser autocomplete completely by setting this to "off". Again this is not possible with the current TextBox but would be easily achievable if I could specify the template for the input area.

If this was implemented as requested I would expect my angular HTML to look something like:

 <kendo-textbox>
   <ng-template kendoTextBoxPrefixTemplate>
       <button kendoButton look="clear" icon="image"></button>
   </ng-template>
   <ng-template kendoTextBoxInputTemplate>
       <input myDirective [autocomplete]="myValue" />
   </ng-template>
   <ng-template kendoTextBoxSuffixTemplate>
       <kendo-textbox-separator></kendo-textbox-separator>
       <button kendoButton fillMode="clear" icon="calendar"></button>
       <kendo-icon name="bell"></kendo-icon>
    </ng-template>
 </kendo-textbox>

The DatePicker control for Angular has a hidden vertical scrollbar on the kendo-virtualization element, which is nested inside the kendo-calendar-navigation and kendo-calendar-viewlist elements. Though it is hidden from view, it is still clickable, and can obscure the selectable dates in the calendar. Clicking it results in activating the scrollbar, which will result in the navigation sidebar scrolling. 

I have attached two screenshots to show the affected areas. Highlighted in red are the areas that when clicked will activate the sidebar scrollbar, and highlighted in blue is the area that will activate the calendar scrollbar, along with their respective elements in the DOM.

It appears the scrollbar is hidden from view via a combination of padding and margin settings from the css below:

.k-calendar .k-content.k-scrollable,
.k-calendar .k-calendar-content.k-scrollable {
    box-sizing: content-box;
    overflow-x: hidden;
    overflow-y: auto;
    display: block;
    padding-right: 100px;
    padding-left: 100px;
    margin-left: -100px;
    margin-right: -117px;
}

I am using Edge Version 105.0.1343.50

Tab Key: When you press the TAB key, the editor loses control of the focus. It is intended to give tab space rather than leave editor control. The indent space actually differs greatly from the tab space.

We are using placeholder like <span id="P_Name" name="P_Name">{P_Name}</span> . this would replace with the patient name on loading the editor. 

we used the ContentEditable = false is not working for the span. Some important content such as patient information should be read-only.

attached the sample editor content , the below content are loading dynamically , so we should restrict user should not edit the conent.

when someone clicks on a date in the middle of the component, it will scroll the component instead of selecting the date.

This occurs in chrome and edge. In firefox this issue is not observed.

Steps:

1. Open a datepicker (https://www.telerik.com/kendo-angular-ui/components/dateinputs/datepicker/)
2. Hover over tuesday (bootstrap theme), between tuesday and wednesday in default theme.
3. Click on the date.
4. The component scrolls instead of selecting the date.

The cursor also changes from pointer to default. It seems another component is on top of the tuesday column.

https://stackblitz.com/edit/angular-e53ira?file=src/app/app.component.ts

If the popup is off-screen, it is simply cut off, unlike vertical which flips it to the other side.

Hi there,

we'd like to raise a change request in relation to column widths on grids:
https://www.telerik.com/kendo-angular-ui/components/grid/columns/width/ 

Currently, we can either set a fixed width on a column, or not set a width at all and leave it dynamic. Our problem is, that we have some columns that would benefit from additional space if it is available (e.g. on a larger screen), yet really suffer if they do not receive enough space. 

When we give such a column a fixed size, we have to choose an amount that will still leave other columns enough space on smaller screens, and since it is fixed, is does not increase in size with larger screens. 

If we don't set a fixed width, (or give all columns a fixed width), the available space will be distributed evenly/proportionally among the columns. So here, the columns do benefit from extra space, but the problem is that on smaller screens, they also can become too small to display the content.

We would like to be able to set a minimum width on columns. We imagine the behavior to be as follows:

If there are some columns with a fixed width and some with a min. width, and

• the available space is less than the sum of the fixed and min. widths -> a horizontal scrollbar is added
• the available space is more than the sum of the fixed and min. widths -> the additional space is distributed among the columns with a min. width (evenly or proportionately, either option is fine)

Would like to have a carousel  component for pictures or carousel-ing through templates

Something like this maybe: https://stackblitz.com/edit/ivycarousel-demo?file=src%2Fapp%2Fapp.component.ts

Issue description: While navigating through page number buttons Screen reader does not identify which page number is selected. Issue is observed with “Narrator” and “NVDA” as well

Test Environment:

Narrator (Windows 11), NVDA (Version: 2022.1)

Repro steps:

1. Hit on the link Overview - Grid - Kendo UI for Angular (telerik.com)
2. Tab navigate to table under “Angular Data Grid Overview”
3. Run Screen reader
4. Tab Navigate to page navigation buttons
5. Observe that Screen reader does not identify which page number is selected

Actual results: While navigating through page number buttons Screen reader does not identify which page number is selected. Issue is observed with “Narrator” and “NVDA” as well

Expected results: While navigating through page number buttons screen reader should identify which page number is selected

Attachments:  Attachments

Hi there,

It would be extremely useful to have some sort of global configuration for component settings / inputs.

For example: I want to remove animation from all of my dropdown lists.

This should be easier. The default workflow is to configure each and every instance of DropDownList using the component's input properties.

Less than ideal workarounds

• Create an angular directive that auto configures a given Kendo component and apply that directive to each instance of your component.
• Wrap a given Kendo component in a custom component, and configure it there. This will break the Kendo component's form integration, and you must implement the wrapper component to account for this.

Thank you.

Please find the below screenshot for your reference and help us

Thanks,

Rajkumar S

Hi

I've started using Filter component since your recent editorTemplate feature makes is more usable when it comes to selecting predefined list of values.

One problem with this is that majority of values for filterable fields are based on predefined list of values that we put in dropdown list.
So our component template has many repeated templates like this

Writing these editor templates with handlers for valueChange that differs only in the source list and using onInit to set these as editorTemplate seems inefficient. 
Our component ended up with mostly filter editor templates just in order to use filter component.
I am aware that this could be all done in markup but using filters property on Filter is more flexible as filters can be driven from server side.

It would be a good that FilterExpression type has some property like valuesListData: {text: string, value: any}[].so that dropdown get generated automatically.
I assume that picking from the dropdown is the mostly used scenario and would satisfy majority use cases.

So this is a feature request:

As a developer I would like to be able to set a list of objects on FilterExpression object so that Filter component create dropdown for value editor with the provided list.

Hello,

we are searching for two components that we don’t find in your ANGULAR Library.

These components are:

• KANBAN Cards / TASK LISTS   
• Docking Manager

I have attached some print screens for existing components on the market...

Could you please check if there are any future/planned  developments concerning these two components with Telerik?

Thank you in advance…

Select all checkbox provided in tree list module is not working as expected. Below are the detailed step to reproduce

To Reproduce

Scenario 1 :

1. Checked on select all checkbox
2. Unchecked any of the row, the select all checkbox still checked.

Scenario 2 with pagination:

1. Checked on select all checkbox
2. Move to next page
3. Select all checkbox is checked, but the rows is not selected

Scenario 3:

1. Checked on select all checkbox
2. Expand the parent node, the child node is not checked

Expected behavior
Scenario 1:
The select all checkbox should be unchecked. Same as what provided in Grid module
Scenario 2:
The select all checkbox should be unchecked
Scenario 3:
The child node need to be checked