Thank you for confirming. I see that you are using a Headless setup and currently the extensibility API is not ready to be able to pin point a particular field in Headless context. A fix is currently being worked on and while we don't have an estimated date for delivery/release. In the Headless cont...

Hi Ricardo, To be able to provide an alternative field renderer in Universal Editor, the field "component" property in the "component-models.json" must match the "dataType" property in the "getRenderers" call. With the code above all field with "component": "image", "media" and "richtext" should get...

Hi Carlos, We have a new feature in the Universal Editor API, that is still undocumented that might just let you do what you want.Using the connection object that you retrieve in the Extension. (https://developer.adobe.com/uix/docs/services/aem-universal-editor/api/commons/#building-extension-ui), y...

This sounds like a bug, know I understand better. I am going to try to reproduce it on my side.

Hey, I'm part of the engineering team supporting this feature. I'm not sure that I understand the problem you face. Would you have some code sample for us to test this behaviour? Thanks.