Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

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

Avatar

Level 1

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 :

pastedImage_17.png

Demo :

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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

View solution in original post

6 Replies

Avatar

Community Advisor

Hi,

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

Screen Shot 2018-06-25 at 3.41.12 PM.png

Screen Shot 2018-06-25 at 3.39.30 PM.png

Thanks

Arun



Arun Patidar

Avatar

Level 1

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

1516041_pastedImage_5.png

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

Avatar

Level 1

Please download the component package from here.

Dropbox - demo.zip

Thanks

Avatar

Correct answer by
Community Advisor

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

Avatar

Level 1

Hi,

After switching to coral3 this is working fine.

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

Thanks

Avatar

Community Advisor

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