-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation on Browse Mode: Remove existing editing functionality #50698
Comments
Working on this now |
I have a PR in #50788 which removes the main edit pieces.
This part is not clear to me. If understand that if you click on a menu item it will currently go to a preview of that page in the Browse Mode. I understand we want to remove that functionality but if we do then what happens if you select a Nav item? Nothing? The issue is that it still needs to be selectable to allow for drag & drop so this feels unusual. |
Just catching up here. I understand that we may be removing the “click to navigate to page” action from the navigation items. For context, initial efforts had the Navigation section act as both content access and basic menu management. With the recent addition of the Pages section, this is less necessary, and if we remove the drilldown from these items we also simplify some of the back button behavior. I still think there can be value in the drilldowns in the navigation section, especially as each drilldown detail increases in value (such as clicking the blog, then changing posts per page), but it is also fine to omit this behavior if it simplifies the process going forward. We can always revisit. |
PR to move the navigate action to the ellipsis menu here: #50843 |
This has been done. |
As part of #50396, the first step is to remove some of the existing functionality from the Navigation List View in Browse Mode, specifically:
The text was updated successfully, but these errors were encountered: