Feature description

Description

Currently, the NavigationMenu component (built on top of Radix UI primitives) is excellent for standard mega menus, but it lacks native support for deep, multi-level nested submenus (e.g., Level 1 ➔ Level 2 ➔ Level 3).

Nesting a secondary <NavigationMenu> inside the parent <NavigationMenuContent> causes severe DOM conflicts, breaks the Radix Viewport animation, and introduces accessibility/aria-attribute errors.

Use Case

This feature is highly essential for structured e-commerce or enterprise navigations that require deep vertical hierarchies, such as:
Computer Components ➔ GPUs ➔ Nvidia / AMD

Proposed Solution

It would be amazing if Shadcn UI could introduce a native sub-trigger primitive architecture for the NavigationMenu component—similar to how <DropdownMenuSub> and <DropdownMenuSubTrigger> work seamlessly within the DropdownMenu component.

Alternatively, providing an official documentation recipe or layout pattern on how to handle multi-column nested state cleanly inside a single NavigationMenuContent viewport would be incredibly helpful for the community.

Additional Context

Using the DropdownMenu inside a NavigationMenu acts as a temporary workaround, but it breaks visual consistency, viewport scaling, and feels like a hacky architecture rather than a unified design system layout.

Affected component/components

No response

Additional Context

Additional details here...

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues and PRs