Skip to content
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 drawer doesn't highlight current route visually #1429

Closed
smares opened this issue Aug 20, 2017 · 4 comments
Closed

Navigation drawer doesn't highlight current route visually #1429

smares opened this issue Aug 20, 2017 · 4 comments
Labels
duplicate The issue has already been reported

Comments

@smares
Copy link

smares commented Aug 20, 2017

Steps to reproduce

Use vue-router and create a navigation drawer with some links, then navigate to one of them.

Versions

Vue 2.4.2, Vuetify 0.14.11, Edge 15.

What is expected ?

The current route should be highlighted visually.

What is actually happening ?

While list__tile--active is applied to the active route that should apply a blue color, the highlight color is overwritten by .application--light .navigation-drawer .list__tile. Also, bear in mind that event without that rule, .application--light .navigation-drawer a, .application--light .navigation-drawer .subheader, .application--light .navigation-drawer .list would take precendence over .list__tile--active

Reproduction Link

https://codepen.io/anon/pen/qXoaqO

@jacekkarczmarczyk
Copy link
Member

That's already fixed on dev branch

@smares
Copy link
Author

smares commented Aug 20, 2017

Is it the same as #1374? If yes, sorry, that title was misleading because the class is applied, it's just that its style is overriden. If it's fixed, please close. 👍

@johnleider
Copy link
Member

Duplicate of #1374

@johnleider johnleider marked this as a duplicate of #1374 Aug 20, 2017
@johnleider johnleider added the duplicate The issue has already been reported label Aug 20, 2017
@lock
Copy link

lock bot commented Apr 16, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord

@lock lock bot locked as resolved and limited conversation to collaborators Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate The issue has already been reported
Projects
None yet
Development

No branches or pull requests

3 participants