-
Notifications
You must be signed in to change notification settings - Fork 80
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
feat: introduce size variants for light navbar #2760
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@@ -48,12 +51,14 @@ function _Navbar(props: ExpandProps<NavbarProps>, ref: React.Ref<HTMLElement>) { | |||
topRightItems, | |||
contentMaxWidth = '100%', | |||
testId = 'cf-ui-navbar', | |||
className, | |||
variant = 'wide', |
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.
Although wide
should be our default, we will have a much easier time migrating to the new Layout if we go with fullscreen
for now. I'm a bit torn, but since it's an alpha I'm thinking we can always switch it to wide
later on. What do you think?
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.
I would rather do the necessary changes now than executing a code-mod later and would go directly with the wide variant as default.
At least this way the fullscreen is a conscious decision from the beginning and we can challenge if its even needed, when it appears to us.
While if we change it later via a code mod we will not think twice over the usage of the fullscreen variant.
But maybe @damann can weight in if fullscreen should be the exception or the norm?
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.
We need fullscreen
everywhere we don't have the page cut. So everywhere but 4 screens.
This enables controlling the size of the navbar content via a dedicated prop instead the need to handover specific width sizes.