-
Notifications
You must be signed in to change notification settings - Fork 13
feat: add global scrolbar style #833
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,21 @@ | ||
| /* Resets for button */ | ||
|
|
||
| button, | ||
| [type='button'], | ||
| [type='reset'], | ||
| [type='submit'] { | ||
| [type="button"], | ||
| [type="reset"], | ||
| [type="submit"] { | ||
| -webkit-appearance: button; | ||
| appearance: button; | ||
| appearance: button; | ||
| background-color: transparent; | ||
| background-image: none; | ||
| } | ||
|
|
||
| /* Global native scrollbar styling — uses the Baseline standard scrollbar | ||
| properties (scrollbar-width / scrollbar-color), supported across Chrome, | ||
| Safari and Firefox. Note: scrollbar-width is keyword-only (no exact px) and | ||
| setting scrollbar-color opts out of the macOS overlay/auto-hide scrollbar. | ||
| Use the <ScrollArea> component where auto-hide / hover-grow polish matters. */ | ||
| * { | ||
| scrollbar-width: thin; | ||
| scrollbar-color: var(--rs-color-overlay-base-a5) transparent; | ||
| } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🧩 Analysis chain
🌐 Web query:
What is the correct modern CSS value for the appearance property on button elements?💡 Result:
The modern, standards-based CSS value is appearance: none; to remove native/platform styling, while appearance: auto; preserves the browser’s native button appearance. If you specifically want to force a “button-like” widget appearance via appearance’s legacy keywords, the value appearance: button; exists, but MDN notes these older values behave like auto and says to use auto instead.[1]
Citations:
Update
appearance: buttontoappearance: autoin reset.cssMDN recommends using
appearance: auto(legacyappearance: buttonkeywords should be avoided even if they behave similarly). Update both the prefixed and unprefixed declarations.🔧 Proposed fix
📝 Committable suggestion
🧰 Tools
🪛 Stylelint (17.12.0)
[error] 8-8: Expected "button" to be "auto" (declaration-property-value-keyword-no-deprecated)
(declaration-property-value-keyword-no-deprecated)
🤖 Prompt for AI Agents
Source: Linters/SAST tools