You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a UI inconsistency regarding the mobile/desktop media query breakpoints at exactly 768px width.
Currently, when the viewport width is exactly 768px:
The Navigation Bar switches to the Desktop view (min-width: 768px).
However, the Search Component still displays in the Mobile view (it seems to switch to desktop only at min-width: 769px).
This creates a mismatched UI state at 768px where the header is in desktop mode, but clicking the search behaves like the mobile version.
Reproduction
Navigation Bar
Search Component
767px
768px
769px
Expected behavior
The breakpoints should be unified. The Navigation Bar and the Search Component should transition from mobile to desktop at the exact same width.
To fix this, the layout breakpoint should probably be adjusted so that the desktop view starts at min-width: 769px (and mobile ends at max-width: 768px), aligning it with the search component's behavior.
System Info
*
Additional context
For now, I managed to fix this issue temporarily by injecting a custom Vite plugin in .vitepress/config.ts
Describe the bug
There is a UI inconsistency regarding the mobile/desktop media query breakpoints at exactly
768pxwidth.Currently, when the viewport width is exactly
768px:min-width: 768px).min-width: 769px).This creates a mismatched UI state at
768pxwhere the header is in desktop mode, but clicking the search behaves like the mobile version.Reproduction
Expected behavior
The breakpoints should be unified. The Navigation Bar and the Search Component should transition from mobile to desktop at the exact same width.
To fix this, the layout breakpoint should probably be adjusted so that the desktop view starts at
min-width: 769px(and mobile ends atmax-width: 768px), aligning it with the search component's behavior.System Info
Additional context
For now, I managed to fix this issue temporarily by injecting a custom Vite plugin in
.vitepress/config.tsValidations