There is a dearth of browser inline editors for Word documents.  It appears that the only viable solution currently out there is to implement WOPI and this standard is complex, poorly documented and extremely difficult to implement.  There are some alternatives out there:

• https://www.zoho.com/officeplatform/integrator/wopi-alternative.html
• https://www.collaboraoffice.com/code/

The former is incredibly expensive because it charges per API call (effectively charging each time a document is opened or edited) and the latter is overly complex and for Linux users.

A further alternative is syncfusion's document editor.  This editor is good but loses formatting.

Surely it would be possible to unravel Word's open xml format and load it into a modified version of the Rich text Editor?

If ComboBox is used in a form and its required, screen readers will not pick up this information since it is not passed on to the underlying input field.

The example a nice workaround, but a final solution should have this automatically implemented by the control.

https://stackblitz.com/edit/angular-2ck3gu

https://stackblitz.com/edit/angular-niog8n-eldomz?file=app%2Fapp.component.ts

I very recently tried to update kendo UI to the latest version (from kendo-default-theme 4.23.0 to latest), and ran into a lot of problems, caused by the fact that I don't use the precompiled css theme styles. (removing the "node_modules/@progress/kendo-theme-default/dist/all.css" from the styles array in angular.json)

It is very opaque which styles needs to be imported for which module, and in what order they to be imported, since that seems to matter too.
Especially because there are no documentation for this at all.

For example, to get the styles for the new kendo-textbox component, the following needs to be imported in the styles.scss, AND in that specific order.

button needs to be first, and forms has to be before textbox and input

@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';

which means that none of the following will compile: 

@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';

@import '~@progress/kendo-theme-default/scss/button/_index.scss';
@import '~@progress/kendo-theme-default/scss/input/_index.scss';
@import '~@progress/kendo-theme-default/scss/forms/_index.scss';
@import '~@progress/kendo-theme-default/scss/textbox/_index.scss';

As i see it there are two reasonable ways to solve this, where the first obviously results in the best user experience:

• Refactor the styles "modules" to be 1:1 with either the angular module or the specific component, so using one module/component results in a single SCSS import only
• Create documentation that very explicitly states what files to import and in what order they need to be imported when using compiled SCSS

Please ensure that ALL kendo components are extended with @Output() onDataBound = new EventEmitter<any|T>();

When using any kendo components that uses dialogs from inside an ionic application, all dialogs experience stacking context issues in iOS.

The solution for this at the moment is to tell every single component to append its dialog(s) to a specified container in a bid to better control its visibility.
Right now, not every component have an 'appendTo' setting for its dialogs (ie: Editor) which makes it unusable on iOS devices.

The feature I would like to request is a way to setup the default 'appendTo' container only once from a core service to any and all dialogs.
This would help in not having to add it manually to every single components we use and maybe make it easier for you to make this feature available to more components with less work. I would make it so it applies to the dialog component and service. (or use different methods to setup each differently)

Here's how it could look like :

@Component({
  selector:    'app-mycomponent',
  templateUrl: './mycomponent.component.html'
})
export class MyComponent implements OnInit {

  public kendoContainer: ViewContainerRef; //This would point to a container.
  
  constructor( private kendoSetupService: SetupService ) {}


  ngOnInit() {
      //This would affect all components using dialogs as well.
    this.kendoSetupService.dialogs.setDefaults({
      'appendTo': this.kendoContainer
    });
  }
}

<kendo-dropdownlist [(ngModel)]="data" [popupSettings]="{ 'appendTo': kendoContainer }"></kendo-dropdownlist>

This service could be used to override many of the kendo default behaviors with minimal code footprint in the end.
It could be divided into smaller default services instead if you prefer such as DialogSetupService

Hi,

Can we have a word cloud component on the Kendo UI for Angular?

Thanks,

Not sure if this is a bug in Angular CLI, Karma, or Kendo. I wrote up a bug for Angular CLI for this as well: https://github.com/angular/angular-cli/issues/20449

Issue only tested on Windows 10 x64 with Chrome 89 installed.

1. Create new application:
   ng new <app-name> --strict=true --style=scss --routing=true
2. Install @progress/kendo-theme-default
npm install @progress/kendo-theme-default --save
3. Open styles.scss, add the following line:
   @import "~@progress/kendo-theme-default/scss/all";
4. Open karma.conf.js and change the following properties:

    autoWatch: false
    browsers: ['ChromeHeadlessCI'],
    customLaunchers: {
      ChromeHeadlessCI: {
        base: 'ChromeHeadless',
        flags: ['--no-sandbox']
      }
    },
   singleRun: true

5. Run ng test

After 2+ minutes, warning in console shows: WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
Then, NFO [launcher]: Trying to start ChromeHeadless again (1/2).
The second time launches without issue.

If you remove the line from styles.scss and repeat ng test, the problem is not visible.

Alternatively, check out this repo and run ng test :https://github.com/acohenOT/unit-testing

Warning indicated below:

Karma v6.1.2 server started at http://localhost:9876/
05 04 2021 12:20:05.510:INFO [launcher]: Launching browsers ChromeHeadlessCI with concurrency unlimited
05 04 2021 12:20:05.536:INFO [launcher]: Starting browser ChromeHeadless
- Generating browser application bundles (phase: building)...05 04 2021 12:22:32.075:WARN [launcher]: ChromeHeadless have not captured in 60000 ms, killing.
/ Generating browser application bundles (phase: building)...05 04 2021 12:22:32.986:INFO [launcher]: Trying to start ChromeHeadless again (1/2).
√ Browser application bundle generation complete.
05 04 2021 12:22:39.009:INFO [Chrome Headless 89.0.4389.114 (Windows 10)]: Connected on socket 6ClQVkn2c_tOxxhlAAAB with id 89607273
Chrome Headless 89.0.4389.114 (Windows 10): Executed 3 of 3 SUCCESS (0.305 secs / 0.217 secs)
TOTAL: 3 SUCCESS

While the grid is initially loading data, the "No records available." message is confusing and provides no useful information.

Expected behavior - when the grid is initially loading, don't display the message as the rows/data might very well appear

To reproduce basically just go to the grid demo page (refresh if needed) and pay attention to the grid loading: https://www.telerik.com/kendo-angular-ui/components/grid/data-binding/

Example in our project - intuitively you'd think that the grid has no records until you see the loader; in any case, the message looks out of place:

Current column management is dealt with horizontally, dragging columns left and right.

Current visibility management is dealt with vertically, ticking columns on and off.

With horizontal management, only 5-10 columns fit on a screen.

With vertical management, there is potential to fit 5x or more columns on a screen.

Our customers often have around 100 columns, and need to reorder frequently.

They are asking for more easy column management.

Other grid/table solutions often offer an edge-auto-scroll feature, which I have seen a Feature Request here and have upvoted it.

But we strongly feel that a vertical arrangement, such as the one already existing in the Column-Context-Menu, could provide our customers with a better UX.

Many thanks.

For example, if I am using the Kendo Splitbutton, the popup should have a class like ".k-split-button-popup". This will make it far easier to style the popups based on their "parent" or "creator".

For now, I am using the popupSettings, but I think it would be beneficial for it to be automatic.

When using the calendar dropdown of the datetimepicker... the user has the ability to click a date part and then click "set" and a the time part is defaulted to a value:

Which results in a full valid datetime if the user doesn't particularly care about the time part:

However, if the user prefers to type in their selection and still doesn't care about the time part... they are left with an invalid value:

They are forced to type in a time part they don't care about which is a waste of time and effort.

Can we get an option to provide a "default autofill value" for the time part so that quick keyboard entry is possible?

There is no event to cater mouse-over events for a specific cell of a row in k-grid. This is important if we need to perform something cell specific like pop up a dynamic component 

related to that cell and row.

Hi All,  

    Anyone can help us to figure it out?

   Currently, We are using Angular Kendo Gird package, and got issue for tooltip message for Gird.

        When We mouse move over 3 dots for grid column menu, we would get strange tooltip message,  for details , please check it from attachment.

         My Email:liji.tao@teranet.ca

Thanks

Liji

Hi Team,

Allow the ability to change the styling on the inner input of the component. This will allow developers easy access to change the placeholder styling based on condition or overall input element. Currently, a custom implementation like the following can be used:

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

or with a directive:

https://stackblitz.com/edit/angular-pzv7zc-v4te8u?file=app%2Fapp.component.ts

Thanks.

Currently it is not possible to touch-scroll the locked section of the Grid on mobile devices - this is a known limitation:

https://www.telerik.com/kendo-angular-ui/components/grid/columns/locked/#toc-known-limitations

https://www.telerik.com/kendo-angular-ui-develop/components/treelist/columns/locked/#toc-known-limitations

Please provide the opportunity for touch-scrolling the locked section of Grid and TreeList similar to the one available on other devices via the mousewheel.

Hi team,

It will be a good addition to the library to have a MultiColumnDropDownList component similar to the already existing MultiColumnComboBox.

Thank you.

Hi,

If we format kendo-datepicker to (MMMM/dd/yyyy) and if we enter number of month in input then it is not reflecting and shows month in input field.

As you can see in screenshot, I called (valueChange) event to see the changed value, I have enter 10 in month input field so it shows two value in console, first one is when 1 is press and second is when 0 is pressed after 1 so it gives null and in input field it shows month instead of October.

It is working if we enter first letter of month but it should work if we enter month in number.

Please fix this issue asap.

Thanks.