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

Improved the text selection style #1497

Merged
merged 1 commit into from
Nov 28, 2024
Merged

Improved the text selection style #1497

merged 1 commit into from
Nov 28, 2024

Conversation

samejr
Copy link
Member

@samejr samejr commented Nov 25, 2024

Improved the text selection colours

Summary by CodeRabbit

  • New Features
    • Enhanced text selection styles for improved visual feedback when users select text.

Copy link

changeset-bot bot commented Nov 25, 2024

⚠️ No Changeset found

Latest commit: d5936a4

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
Contributor

coderabbitai bot commented Nov 25, 2024

Walkthrough

The changes made in this pull request involve the addition of new styles for text selection in the tailwind.css file. Two new rules have been introduced under the @layer base directive for the ::selection and ::-moz-selection pseudo-elements, which specify a background color and text color for selected text. No other modifications were made to existing styles or structures.

Changes

File Change Summary
apps/webapp/app/tailwind.css Added styles for ::selection and ::-moz-selection with background color bg-text-bright/30 and text color text-text-bright.

Poem

In the garden where colors play,
New styles bloom in a bright array.
When you select, a glow so fine,
Text dances bright, a joy divine!
With every click, a cheerful sight,
Thanks to changes, all feels right! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint (1.23.1)

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

apps/webapp/app/tailwind.css

(node:20535) ESLintIgnoreWarning: The ".eslintignore" file is no longer supported. Switch to using the "ignores" property in "eslint.config.js": https://eslint.org/docs/latest/use/configure/migration-guide#ignoring-files
(Use node --trace-warnings ... to show where the warning was created)

Oops! Something went wrong! :(

ESLint: 9.15.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.


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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3792394 and d5936a4.

📒 Files selected for processing (1)
  • apps/webapp/app/tailwind.css (1 hunks)
🔇 Additional comments (1)
apps/webapp/app/tailwind.css (1)

17-23: Well-structured implementation of text selection styles!

The implementation follows best practices by:

  • Including both standard and Mozilla-specific selectors
  • Using semantic color tokens
  • Maintaining consistent styling

Comment on lines +18 to +23
::selection {
@apply bg-text-bright/30 text-text-bright;
}
::-moz-selection {
@apply bg-text-bright/30 text-text-bright;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Selection colors need adjustment for better contrast

Based on the tailwind configuration, the current selection colors may have accessibility issues:

  • text-bright is set to charcoal[200] (#D7D9DD), which is a light gray
  • The background is set to 30% opacity of this same color (bg-text-bright/30)
  • This combination likely doesn't provide sufficient contrast against the dark theme background (charcoal[800] #1A1B1F)

Recommendations:

  • Consider using a higher opacity value for the selection background (e.g., 50% or higher)
  • Or use a different color token with better contrast against both selected text and background, such as lavender[400] (#826DFF) which is already used for text links
🔗 Analysis chain

Verify color contrast for accessibility

Please ensure that the selected text maintains sufficient contrast ratio with the background color (bg-text-bright/30) across both light and dark themes for accessibility compliance.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for theme-specific color definitions that might affect text selection contrast

# Look for color token definitions that might affect text selection
rg -A 5 "text-bright|background" "tailwind.config"

# Check for theme-specific color variations
rg "theme:" -A 10 "tailwind.config"

Length of output: 196


Script:

#!/bin/bash
# Search for tailwind config files in the repository
fd -e js -e ts -e cjs -e mjs "tailwind.config"

# Also check for theme-related configurations in any CSS files
rg -t css "theme|colors?:" -A 5

Length of output: 376


Script:

#!/bin/bash
# Check the actual tailwind config content for color definitions
cat apps/webapp/tailwind.config.js

# Look for any theme-specific styles or color variables in the webapp
rg -t css "theme|--color|color:" apps/webapp/

Length of output: 7064

Copy link

pkg-pr-new bot commented Nov 25, 2024

@trigger.dev/react-hooks

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/react-hooks@1497

trigger.dev

npm i https://pkg.pr.new/triggerdotdev/trigger.dev@1497

@trigger.dev/rsc

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/rsc@1497

@trigger.dev/build

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1497

@trigger.dev/sdk

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1497

@trigger.dev/core

npm i https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1497

commit: d5936a4

@matt-aitken matt-aitken merged commit b7de02e into main Nov 28, 2024
9 checks passed
@matt-aitken matt-aitken deleted the text-selection branch November 28, 2024 11:33
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.

2 participants