# \[Feature or bug?\] Navigation rules visible on editor but can't be set for UUserWidget itself. **URL:** \ **Category:** Issues and Bug Reporting\ **Tags:** unreal-engine, bug-report, editor, Widget, CPP, Blueprint, question, UMG\ **Created:** [April 7, 2023, 7:59pm UTC](https://forums.unrealengine.com/t/feature-or-bug-navigation-rules-visible-on-editor-but-cant-be-set-for-uuserwidget-itself/875240 "2023-04-07T19:59:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Roy\_Wierer.Seda145](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/roy_wierer.seda145/32/906551_2.png) [@Roy\_Wierer.Seda145](https://forums.unrealengine.com/u/Roy_Wierer.Seda145)\ **Post date:** [April 7, 2023, 7:59pm UTC](https://forums.unrealengine.com/t/feature-or-bug-navigation-rules-visible-on-editor-but-cant-be-set-for-uuserwidget-itself/875240/1 "2023-04-07T19:59:50Z")
As the title says, you can’t set the navigation rules on a UUserWidget itself from the editor panel, or any rule you choose reverts to “escape”. Some widgets which you absolutely don’t want to navigate out of (think menu on top of a menu, or a blocking dialog panel) do need the navigation rules to be set to “Stop”. The current workaround is to get the root widget added to its hierarchy and set the rules there, during PreConstruct. This is rather ugly since we can’t (or shouldn’t) do this during the c++ constructor of the UUserWidget and are writing settings to another innocent widget during PreConstruct. Request: Make it possible to set navigation rules on a UserWidget level. ---
**Author:** ![NoTime.Tech](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NoTime.Tech](https://forums.unrealengine.com/u/NoTime.Tech)\ **Post date:** [April 3, 2026, 8:14pm UTC](https://forums.unrealengine.com/t/feature-or-bug-navigation-rules-visible-on-editor-but-cant-be-set-for-uuserwidget-itself/875240/2 "2026-04-03T20:14:30Z")
Where are we at with this?