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

[Bug Report][3.1.4] Data attribute not added to v-navigation-drawer while using scoped attribute in style tag #16646

Closed
taozhiyu opened this issue Feb 12, 2023 · 3 comments
Labels
upstream Problem with a third party library that we may have to work around wontfix The issue is expected and will not be fixed

Comments

@taozhiyu
Copy link

taozhiyu commented Feb 12, 2023

Environment

Vuetify Version: 3.1.4
Vue Version: 3.3.0-alpha.4
Browsers: Chrome 110.0.0.0
OS: Windows 10

Steps to reproduce

After adding the range attribute to the style tag, the style did not work. After testing, this is caused by the v-navigation-drawer not adding data-v-* block information, other components were not tested.

Expected Behavior

scoped tag works in v-navigation-drawer

Actual Behavior

it does not work

Reproduction Link

https://play.vuetifyjs.com/#...

@mediafreakch
Copy link
Contributor

Workaround is to use :deep() selector. Here's an updated example.

As far as I can see, v-navigation-drawer is a multi-root component where attribute fallthrough needs to be taken care of manually (class attribute forwarding missing?)

@taozhiyu
Copy link
Author

taozhiyu commented Apr 5, 2023

I know that this approach does solve the problem, but I think it should be considered a component defect? It actually defeats the purpose of the "scope" approach.

Thanks anyway.

@KaelWD
Copy link
Member

KaelWD commented Apr 5, 2023

vuejs/core#5446

data-v-* is added by vue and is skipped on multi-root components.

@KaelWD KaelWD closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2023
@KaelWD KaelWD added wontfix The issue is expected and will not be fixed upstream Problem with a third party library that we may have to work around and removed S: triage labels Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Problem with a third party library that we may have to work around wontfix The issue is expected and will not be fixed
Projects
None yet
Development

No branches or pull requests

3 participants