-
Notifications
You must be signed in to change notification settings - Fork 25
feat: add top bar logo for mobile view #1281
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
Conversation
651ef21 to
d61e8c2
Compare
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.
Pull Request Overview
This PR adds mobile logo support to the top bar by introducing a responsive logo display mechanism that shows different logos based on screen size. The changes enable customizable logos for mobile viewports while maintaining backward compatibility.
- Added responsive picture element with media queries for mobile logo display
- Extended theme configuration to support optional mobile logo property
- Updated extension SDK with Tailwind CSS configuration and documentation
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/web-runtime/src/components/Topbar/TopBar.vue | Added responsive picture element to display mobile-specific logo |
| packages/web-pkg/src/composables/piniaStores/theme.ts | Added logoMobile property to theme schema |
| packages/extension-sdk/tailwind.css | New Tailwind CSS configuration for extensions |
| packages/extension-sdk/README.md | Added documentation for Tailwind CSS usage |
| packages/design-system/docs/gettingStarted/tailwindMigration.md | Added note about Tailwind prefix requirements |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| <picture> | ||
| <source | ||
| :srcset="currentTheme.logoMobile ? currentTheme.logoMobile : currentTheme.logo" | ||
| media="(max-width: 639px)" |
Copilot
AI
Sep 29, 2025
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.
The hardcoded breakpoint value 639px should use a CSS custom property or design system token to maintain consistency with other responsive breakpoints in the application.
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.
not supported by media query
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.
There is a brief moment before the 639px are reached where the bigger logo starts to be shrinked because we're running out of space horizontally. Just tested around with the bigger breakpoint, 959px also feels good. What do you think? Approving anyway, because this works flawlessly. 🥳
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 think that's fine, we can use the "higher" breakpoint
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
31907a0 to
ce13a9f
Compare
kulmann
left a comment
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.
Nice improvement! 😍
| <picture> | ||
| <source | ||
| :srcset="currentTheme.logoMobile ? currentTheme.logoMobile : currentTheme.logo" | ||
| media="(max-width: 639px)" |
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.
There is a brief moment before the 639px are reached where the bigger logo starts to be shrinked because we're running out of space horizontally. Just tested around with the bigger breakpoint, 959px also feels good. What do you think? Approving anyway, because this works flawlessly. 🥳
Description
desktop viewport
mobile viewport
Related Issue
How Has This Been Tested?
Types of changes