Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Should start explanded #48

Open
jedmccaleb opened this issue Feb 16, 2016 · 3 comments
Open

Should start explanded #48

jedmccaleb opened this issue Feb 16, 2016 · 3 comments

Comments

@jedmccaleb
Copy link
Contributor

If we are going with collapsable side nav I think it should at least start expanded.

@irisli
Copy link
Contributor

irisli commented Feb 18, 2016

Which one should start expanded? Everything should start expanded?

I think the original intent for collapsible side nav was to compact things so that users would not have to scroll as much and see as many options.

If we have it start expanded, would we want to store local data in the browser to remember which ones were expanded?

If we want to have everything start expanded, then I think we should not have any collapsibleness (which I believe we shouldn't have a collapsable nav anyways).

@jedmccaleb
Copy link
Contributor Author

I would start with everything expanded. I get what you are saying since that this is moving between pages rather than just being a single page it gets weird.

@jessica-collier how are you feeling about the collapsibleness now that you can see it in action?

@irisli
Copy link
Contributor

irisli commented Feb 18, 2016

Note that the current glitches (single line highlighting and current item not collapsible) are byproducts of having the blue rectangle at the side of the current item.

It is documented in the PR #46:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants