Skip to content
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: rounded corner shadow bug #4253

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

CORCTON
Copy link

@CORCTON CORCTON commented Dec 7, 2024

Closes #

📝 Description

This PR fixes the issue with the incorrect display of rounded corner shadows on the official website. The shadow was not being rendered correctly in certain browsers, and this update addresses that problem.

⛳️ Current behavior (updates)

The rounded corner shadows on the website are displayed incorrectly in some browsers. This visual issue impacts the overall design and user experience.

🚀 New behavior

After this fix, the rounded corner shadows are displayed correctly across all supported browsers. The visual appearance of the website is now consistent with the intended design.

💣 Is this a breaking change (Yes/No):

No

📝 Additional Information

This fix primarily affects the visual rendering of the rounded corner shadows on the website. No major changes to functionality or behavior were introduced.

WX20241207-115737@2x

@CORCTON CORCTON requested a review from jrgarciadev as a code owner December 7, 2024 03:58
Copy link

changeset-bot bot commented Dec 7, 2024

⚠️ No Changeset found

Latest commit: 5ff3ea8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Dec 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 7, 2024 4:04am
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 7, 2024 4:04am

Copy link

vercel bot commented Dec 7, 2024

@CORCTON is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Dec 7, 2024

Walkthrough

The pull request introduces updates to the shopCartStyles object in the styles.ts file, specifically enhancing the imageWrapper and sizeOption properties within the modern variant. The imageWrapper now includes an additional class for improved styling, while the sizeOption property has been modified to enhance accessibility with a new focus ring class. Other properties, including button styles, have also been adjusted for better visual presentation. The default variants remain unchanged.

Changes

File Path Change Summary
apps/docs/components/marketing/custom-themes/styles.ts Modifications to shopCartStyles: updated imageWrapper with rounded-3xl and shadow-lg, added focus ring class to sizeOption, and adjusted button styles for font size and rounded appearance. Type export for ShopCartProps updated.

Possibly related PRs

Suggested labels

👀 Status: To Review

Suggested reviewers

  • wingkwong
  • jrgarciadev

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

🧹 Outside diff range and nitpick comments (1)
apps/docs/components/marketing/custom-themes/styles.ts (1)

90-90: Consider standardizing border radius values

While the shadow fix addresses the visual bug, there's an inconsistency in border radius values:

  • imageWrapper uses rounded-3xl
  • img uses rounded-lg
  • wrapper uses rounded-3xl

This might cause subtle visual artifacts in some browsers where the shadows and rounded corners don't align perfectly.

Consider standardizing the border radius:

- "shadow-lg rounded-3xl",
+ "shadow-lg rounded-3xl overflow-hidden",

Also update the img class to match:

- "rounded-lg",
+ "rounded-3xl",
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d9ae7c8 and 5ff3ea8.

📒 Files selected for processing (1)
  • apps/docs/components/marketing/custom-themes/styles.ts (1 hunks)
🔇 Additional comments (1)
apps/docs/components/marketing/custom-themes/styles.ts (1)

89-91: Verify shadow rendering across browsers and backgrounds

The shadow implementation varies between themes:

  • modern: uses shadow-lg
  • elegant: uses shadow-xl
  • retro: uses before:shadow-md

Let's verify the shadow rendering consistency.

✅ Verification successful

Shadow implementation is consistent across themes and browsers

The codebase analysis shows:

  • All shadow implementations use Tailwind CSS classes (shadow-*) which are consistently implemented across browsers
  • The theme variations (shadow-lg, shadow-xl, before:shadow-md) are part of a well-structured design system defined in packages/core/theme/src/
  • No browser-specific shadow implementations were found
  • Shadow styles are properly scoped with appropriate color variants and opacity values
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for all shadow-related implementations to ensure consistency
rg -n "shadow-[a-zA-Z]+" --type ts

# Search for potential browser-specific shadow implementations
rg -n "@(webkit|moz|ms).+shadow" --type ts

Length of output: 24298

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant