Skip to content

fix: checkbox style fixes #226

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 3 commits into from
Aug 16, 2018
Merged

Conversation

aldeed
Copy link
Contributor

@aldeed aldeed commented Aug 16, 2018

Impact: minor
Type: bugfix

Changes

When I pulled the Checkbox into the Reaction Meteor app, it did not display correctly. This was mostly due to using rems. I've switched it to using ems and pixels as appropriate. For most values, em makes sense because as the font size of the checkbox label increases, it looks best if the checkbox increases proportionally.

Also adds isFormInput = true static property on Checkbox. Without this, it does not work correctly within a ReactoForm form.

Breaking changes

None

Testing

Verify that the Checkbox component looks good in various browsers and if you play with the font-size of the label and the html root, everything continues to look good.

@aldeed aldeed self-assigned this Aug 16, 2018
@aldeed aldeed requested a review from machikoyasuda August 16, 2018 14:30
@aldeed aldeed added this to the Kit Carson milestone Aug 16, 2018
@machikoyasuda
Copy link
Contributor

machikoyasuda commented Aug 16, 2018

🚀 Preview deployed

Built with commit 2954100

https://deploy-preview-226--stoic-hodgkin-c0179e.netlify.com

@machikoyasuda machikoyasuda merged commit 824a5e8 into master Aug 16, 2018
@machikoyasuda machikoyasuda deleted the fix-aldeed-checkbox-style-fixes branch August 16, 2018 16:39
@rc-publisher
Copy link
Collaborator

🎉 This PR is included in version 0.21.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

3 participants