-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Fix Safari logos not showing on home page #495
base: main
Are you sure you want to change the base?
Conversation
Update the LinkButton component in the GettingStarted section of the home page. Change the className attribute to use grid instead of flex. This prevents a bug on Safari where the logos would not render.
WalkthroughThe pull request modifies the Changes
Assessment against linked issues
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Visit the preview URL for this PR (updated for commit 9e8eb0d): https://game-ci-5559f--pr495-fix-safari-getting-s-dzz9eow9.web.app (expires Wed, 22 Jan 2025 23:41:15 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 1f0574f15f83e11bfc148eae8646486a6d0e078b |
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/components/pages/home/section/getting-started.tsx (1)
32-35
: Consider adding accessibility attributes to the Link component.While the styling looks great, we could enhance accessibility for screen readers by adding:
- An
aria-label
to describe the action- A
role="button"
since it's styled as a button<Link to={url} + role="button" + aria-label={`Get started with ${url.split('/')[2]}`} className="group grid place-items-center border-gray-600 border-solid rounded-sm border-2 px-6 py-3 w-[180px] h-[70px] transition-all duration-200 hover:scale-110 hover:bg-gray-600" >
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/pages/home/section/getting-started.tsx
(1 hunks)
🔇 Additional comments (1)
src/components/pages/home/section/getting-started.tsx (1)
33-33
: Excellent improvement to the button layout!The switch from flex to grid with
place-items-center
is a great choice here. This approach:
- Provides more reliable centering behavior
- Reduces the number of required CSS properties
- Maintains consistent alignment across different browsers
Closes #493
This pull request includes a small change to the
src/components/pages/home/section/getting-started.tsx
file. The change modifies theclassName
property of theLink
component to use a CSS grid layout instead of flexbox.src/components/pages/home/section/getting-started.tsx
: Changed theclassName
property in theLinkButton
component fromflex
togrid
for centering items.Summary by CodeRabbit