Maciej Bukowski

Hi, thanks for the report! It looks like it's more a problem with the builder, not the integration, but it's hard  to guess. Could you post your build id so...

I'm not sure if that can be easily achieved right now. I've found this guide - https://material.angular.io/guide/creating-a-custom-form-field-control, but it'd require few changes in the `` component. I'll try to dig...

I've created a POC on the [t/21](https://github.com/ckeditor/ckeditor5-angular/tree/t/21) branch - you can see how it's implemented. But we won't be able to ship with the current solution as it depends directly...

> I just found ckeditor supports a tagName so it is able to create a . I'm wondering if the directive matInput can be added there and use a renderer...

Could make more clear how you made the template configurable? Maybe I misunderstood something, but the whole approach seems wrong to me because: 1. You use `matInput` on the `textarea`...

> Maybe we don't have to make it work like a matInput since ckeditor should handle most of the functions, but we can make it looks like a matInput. But...

I'd go with a separate component which would proxy some inputs and outputs. But I'm not sure how easy and clean that solution would be.

For now, I think that this should be another library, let's say `ckeditor5-material-angular` that would depend on the `ckeditor5-angular` as I don't see any valid approach to support the Material...

Thanks for the research @naveedahmed1! > Actually is a component used to wrap Angular Material components and apply common Text field styles such as the underline, floating label, and hint/error...

Hi, @wynfred. Sorry for the delay. I've just checked the integration with the material design directives that you provided. I've got some small issues that would be needed to fix...