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

[BUG] - stroke-width Not Applied Correctly to Checked Icon #4802

Closed
kimskovhusandersen opened this issue Feb 6, 2025 · 1 comment · Fixed by #4811
Closed

[BUG] - stroke-width Not Applied Correctly to Checked Icon #4802

kimskovhusandersen opened this issue Feb 6, 2025 · 1 comment · Fixed by #4811
Assignees
Labels
🎨 Scope : Themes / Styles Related to the themes or styles 🐛 Type: Bug Something isn't working

Comments

@kimskovhusandersen
Copy link

kimskovhusandersen commented Feb 6, 2025

HeroUI Version

2.6.14

Describe the bug

For the Checkbox component, the checked icon (isSelected: true) does not receive the correct stroke-width despite the class, e.g. stroke-[4px].
The indeterminate icon (isIndeterminate: true) receives the correct stroke-width without issues.

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

Render the checkbox component with isSelected: true and change the stroke-width , e.g. stroke-[4px].
Inspect the generated element in the browser’s DevTools and observe that the stroke-width is not applied as expected to the svg for the checked icon.

Expected behavior

The stroke-width should be correctly applied to the checked icon (isSelected: true), just like it is for the indeterminate icon (isIndeterminate: true).
The inside the checked icon should reflect the expected stroke-width from the class (e.g. stroke-[4px]).

Screenshots or Videos

Image

Operating System Version

macOS

Browser

Chrome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Scope : Themes / Styles Related to the themes or styles 🐛 Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants