@xelaint is this permanently open? Or only open upon initial render?

@xelaint is this permanently open? Or only open upon initial render?

I think it should be permanent. If a user is on next.daff.io/docs/packages/cart/extension, and I refresh the page, the @daffodil/cart tree item should remain expanded so the user knows what page they're on and are able to find the related pages easily. Currently, if I navigate to Extension and refresh the page, the @daffodil/cart tree item is closed.

Ok. If I'm on that page and I click:

What should happen?

Should the click do nothing?

I disagree. I think the feature should only cover what happens on initial render. I also think that it should scroll the active item into view.

So if you're on the "Extension" page and decide to refresh to page, you wouldn't want to see that the Extension page is still the selected item in the sidebar?

What I expect in a sidebar navigation where items are hidden:

1. User can collapse or expand a tree item, but the state resets upon refresh.
2. The selected tree item should be visible at all times.

Based on this UI, how does a user easily know where they are in the nav sidebar?

If a tree item isn't nested (i.e. I click on @daffodil/authorizenet), it's apparent to me that that's the active link. Why shouldn't that be the case for nested tree items?

So if you're on the "Extension" page and decide to refresh to page, you wouldn't want to see that the Extension page is still the selected item in the sidebar?

refreshing the page is an "initial render"

the way I interpret "remain expanded" is that the accordion cannot be closed, even by user interaction.

my proposed UX:

• upon initial render (page load) the accordion that holds the active nested item (if the active one is nested) is expanded
• upon initial render the active nav item is scrolled into view

Gotcha. I interpreted "initial render" as literally the first initial render and nothing after that. I think we're on the same page then.