@vasgurug Use the following propertiessling:resourceType="granite/ui/components/coral/foundation/form/numberfield"step="any"min="0"typeHint="double"

@Vinit_Pillai Use sling:resourceSuperType="/apps/..../text/cq:dialog/content/items/text/items/column/items/text" sling:resourceType="cq/gui/components/authoring/dialog/richtext"  

@Vinit_Pillai background: url(${properties.fileReference @ context='styleString'}) no-repeat; 

@hamidk92094312  Request for Feature Enhancement (RFE) Summary :Radio buttons as a data type in AEM Content Fragment model editor.Use-case:Most of the time we get the requirement from the client to choose any field from the available options by using the radio button with the required validation. ex...

Description -Currently, the content fragment model editor does not contain a radio data type.Why is this feature important to you -Most of the time content fragment contains some data like selecting gender. for this kind of work, we have to use the dropwon data type.for refrennce,I have written one ...

@yuriadizes you need to contact the person in your organization who handles all the Adobe accounts or who has Administrator rights.

@Timo_HH It mainly happens because of CSS when div tag contains global styling as follows.   div{ height: 100px; }  try to apply class-specific CSS to avoid such issues. or you can also write some custom CSS for clientlib categories named cq.authoring.editor.core 

@dds3455 This happens mainly because of invalid references. There might be a possibility that someone has removed the old component or so. Please check the error.log and see the root cause issue and try deleting that resource or remove the reference from the page.This might help you to resolve your ...

@ranadyutis95334 I know there is some limitation for the AEM OOTB assets reports generator but you can use the ACS commons report generator tool by specifying queries as per your requirement.https://adobe-consulting-services.github.io/acs-aem-commons/features/report-builder/index.html   

@Ashwin_Raju correct way to write the expression is as follow${slingModel.shouldHaveSelector ? slingModel.someLink  : slingModel.someLink @ selectors='content', extension = 'html' } but in your case please rewrite the logic as<sly data-sly-test={slingModel.shouldHaveSelector}> {slingModel.somelink @...