How to remove class "section" from the wrapper element of a component? | Community
Skip to main content
A
alessandronicif
Level 2
October 16, 2015
Solved

How to remove class "section" from the wrapper element of a component?

  • October 16, 2015
  • 4 replies
  • 1963 views

Hello,

to customize the wrapper element of a component (the one which AEM automatically adds) I'm adding the node "cq:htmlTag", with the following properties:

  • cq:tagName = div
  • class = thumbnail

With this setting, in the html output of the component I see

<div class="thumbnail section"> .... </div>

 

How can I say to AEM to not write the class "section"?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

alessandroniciforo wrote...

My usecase is that the design of the templates is being done independently, at the time being. So I'd like to avoid any possible conflict.

Anyway, I would expect that any additional class used internally by the software, not customizable, use a namespace to avoid conflicts with an already existing css (especially with a common name such as "section"). It's awful that it uses "section" instead of "cq-section" or "aem-section".

 


File a daycare request

4 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

what is your usecase?    Section is used internally for run mode to provide various functionality & I would advise not to remove.  Instead create different css rules.

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

You can create a div with class 'thumbnail' under 'section' div and customize your css accordingly.

A
alessandronicifAuthor
Level 2
October 16, 2015

My usecase is that the design of the templates is being done independently, at the time being. So I'd like to avoid any possible conflict.

Anyway, I would expect that any additional class used internally by the software, not customizable, use a namespace to avoid conflicts with an already existing css (especially with a common name such as "section"). It's awful that it uses "section" instead of "cq-section" or "aem-section".

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

alessandroniciforo wrote...

My usecase is that the design of the templates is being done independently, at the time being. So I'd like to avoid any possible conflict.

Anyway, I would expect that any additional class used internally by the software, not customizable, use a namespace to avoid conflicts with an already existing css (especially with a common name such as "section"). It's awful that it uses "section" instead of "cq-section" or "aem-section".

 


File a daycare request

Terms & ConditionsAccessibility statement

Loading footer...