AEM 6.3 - How to remove "u-coral-noPadding" css class from cq dialog | Community
Skip to main content
ankushj18225577
ankushj18225577
June 25, 2018
Solved

AEM 6.3 - How to remove "u-coral-noPadding" css class from cq dialog

  • June 25, 2018
  • 6 replies
  • 1704 views

I am facing an issue with my dialog.

Issue: When we are using RTE within a dialog, the navigation tabs disappear in fullscreen mode.

Analysis:  u-coral-noPadding  is appending in coral-dialog-content html element. This is only happening when we are using RTE within a dialog.

Screenshot :

Demo :

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 arunpatidar

Hi,

I've just check your package. you are using coral2 components. can you please change all your component to Coral3 e.g. granite/ui/components/coral/foundation/tabs and create structure like I shared in screenshot.

More details about coral3 Migration Guide to CoralUI 3-based — Granite UI 1.0 documentation 

Thanks

Arun

6 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 25, 2018

Hi,

Are you using granite components or coral2. I tried with granite components, works for me.

Thanks

Arun

Arun Patidar
ankushj18225577
ankushj18225577Author
June 26, 2018

Hi arunp99088702 I am using cq/gui/components/authoring/dialog/richtext as sling:resourceType type.

Please see the demo here Dropbox - Jun-25-2018 19-17-02.mp4

ankushj18225577
ankushj18225577Author
June 26, 2018

Please download the component package from here.

Dropbox - demo.zip

Thanks

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
June 26, 2018

Hi,

I've just check your package. you are using coral2 components. can you please change all your component to Coral3 e.g. granite/ui/components/coral/foundation/tabs and create structure like I shared in screenshot.

More details about coral3 Migration Guide to CoralUI 3-based — Granite UI 1.0 documentation 

Thanks

Arun

Arun Patidar
ankushj18225577
ankushj18225577Author
June 26, 2018

Hi,

After switching to coral3 this is working fine.

Do you have any idea how to fix this in coral2?

Thanks

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 26, 2018

I'll recommend, always use Granite/Coral3 components because Coral3 is improvement over Coral2 components.

I'll check for coral2 to make it work.

Thanks

Arun

Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...