-
Notifications
You must be signed in to change notification settings - Fork 88
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
Put the children of AppNavigationItem outside of the main item #2704
Conversation
In the current implementation, a side effect is that it disables the ability to pass class="active" directly to the AppNavigationItem. Signed-off-by: Quentin Guidée <[email protected]> Update src/components/AppNavigationItem/AppNavigationItem.vue Update src/components/AppNavigationItem/AppNavigationItem.vue
Signed-off-by: Raimund Schlüßler <[email protected]>
Signed-off-by: Raimund Schlüßler <[email protected]>
Signed-off-by: Raimund Schlüßler <[email protected]>
@GretaD I fixed some more issues (collapsing didn't work, children were not styled correctly, pinning was broken, see my commits). I would suggest you test it again with Mail, and ideally with Calendar as well, probably. |
Signed-off-by: Raimund Schlüßler <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let move on then, the component works fine on mail(i tested it) and on tasks(Raimund tested it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Originally created by @quentinguidee in #2572:
This change is necessary for #2571 (see why in action: #2571 (comment)). It puts AppNavigationItem's children out of the parent item, and displays them separately. This is the simplest implementation I found without recoding the entire AppNavigationItem. I'm open to ideas if you find something cleaner.
before.mov
after.mov
Important notes/questions to reviewers
In the current implementation, a side effect is that it disables the ability to pass (like in the doc)
class="active"
directly to the AppNavigationItem. It seems like the only purpose of passing theclass="active"
directly is only for the example? TheisActive
property works fine and continues to push the blue background.As another side effect of this PR, when hovering a child, it doesn't display the hover background of the parent (as demonstrated in the screenshots). I can go back to the first one easily if needed. Just unsure if it was a bug or not.