Drawer - Refine Drawer Usage for Better Integration with External Components

Describe the problem

This arose from fixing a layout bug with the drawer component in PR #4142.

Using DrawerPanelContent within an externally provided DrawerPanelContent (in this case from PF Topology) breaks the layout of the sidebar panel.

• Addressed by removing the nested DrawerPanelContent and directly applying DrawerHead and DrawerPanelBody within the DrawerPanelContent that is externally provided from TopologyView.

In our use case, the utility class pf-v6-u-p-md was applied to get the same padding, but this workaround highlights a gap in the current implementation.

How do you reproduce the problem?

See https://github.com/opendatahub-io/odh-dashboard/pull/4142.

Expected behavior

PatternFly needs an improved way to structure and compose standard drawer elements like DrawerHead and DrawerPanelBody within an external DrawerPanelContent wrapper from the TopologyView.

Is this issue blocking you? No.

What is your product and what release date are you targeting?
RHOAI

Commencez par PR #4142 et l’utilisation par TopologyView d’un DrawerPanelContent fourni en externe. Examinez comment DrawerHead et DrawerPanelBody sont composés au sein des composants du drawer, puis reproduisez le scénario de mise en page de la sidebar. Le travail est terminé lorsque les éléments standard du drawer s’intègrent au wrapper externe sans le workaround nested-content ni classe de padding manuelle.