Closed joker23 closed 1 week ago
Tagging this also to the more composable page header discussion in #4632. Keeping this in triage until we have more chance to discuss this one with @ljcarot more.
While we could wait until the composable page header work comes about, it may be worth discussing if we want to support additional types in the meantime to unblock teams or if there are other implications that we’re not ready to enable without more design consideration.
Hey @joker23, can you join an upcoming office hours to give some more detail here?
This issue is stale because it has been open for 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will be closed in 14 days.
This issue was closed because it has received no activity for 14 days.
The problem
Originally, the pageheader component supported having dropdown menus; however, after the typescript migration, that is no longer the case. This enhancement request for that capability to be implemented in typescript. This is used right now in our product:
The solution
We should have feature parity with the original pageheader (or provide a way to reference the original page header implementation while the typescript implementation is no fully compatible with the original design.
Design link
No response
Links to other materials
Relates to https://github.com/carbon-design-system/ibm-products/issues/4632
Owner/main maintainer(s)
?
Second/backup maintainer(s)
No response
Product/offering
No response
Business priority
High Priority = pressing release
Code of Conduct