-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
'#nav-screen-content-after' does not work when screen width between [768,1280) #3773
Comments
No it doesn't. It is only shown on mobile when expanded - https://stackblitz.com/edit/vite-tbadgd?file=docs%2F.vitepress%2Ftheme%2FLayout.vue ![]() ![]() |
'#nav-bar-content-after' also not work, so the question will be how can I add custom component after the nav content when the windows resize to [768,1280)? |
Hi, please check below snapshot about '#nav-bar-content-after'. Any updates? Is it a bug or a new feature need to be done? Thanks! |
you can do something like this - https://stackblitz.com/edit/vite-hqc3bc?file=docs%2F.vitepress%2Ftheme%2FLayout.vue,docs%2F.vitepress%2Ftheme%2FFoo.vue ? |
Hi, that is not what I want. I think the foo menu should be folded to the bottom of pop up menus as below when the widow is between [768,1280), any suggetions? |
I think it's acceptable for me '#nav-bar-content-after' slot does not move to popup menus automatically when screen size is between 768 and 1280. |
Describe the bug
Hi there,
I want to extend the default theme layout by using '#nav-screen-content-after' slot, but if the screen size is between [768,1280) px, '#nav-screen-content-after' slot does not work.
I suppose all nav slots don't work when the window resize to [768,1280) px.
Please help fix the issue.
Thanks
Reproduction
1.Add '#nav-screen-content-after' layout slot according to https://vitepress.dev/guide/extending-default-theme#layout-slots.
2.Resize screen to [768,1280) px.
3.Nav layout slot component will disappear.
Expected behavior
Resize screen to [768,1280) px and the added layout slot component should be still exist.
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: