-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[TextField][material-next] Add FormLabel and InputLabel components #39483
Conversation
Netlify deploy previewhttps://deploy-preview-39483--material-ui.netlify.app/ @mui/material-next: parsed: +0.42% , gzip: +0.41% Bundle size reportDetails of bundle changes (Toolpad) |
b5b5dc7
to
ebd1433
Compare
9c5d50d
to
7af9d6c
Compare
8444c6e
to
4e69fca
Compare
7ba3c66
to
070f057
Compare
This reverts commit b44b03e.
070f057
to
2e4f9b0
Compare
color: | ||
'color-mix(in srgb, var(--md-comp-form-label-disabled-color), transparent calc(var(--md-comp-form-label-disabled-opacity) * 100%))', |
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.
From: https://una.im/color-mix-opacity/
A neat trick using color-mix
to adjust the opacity of color
✨
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.
👏🏼 also using this in the Chip component. It's very useful for Material You's styles.
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.
Looks good to me 😄
As it has the Material You implementation, we should have someone from the design team review it from a design perspective, could you request a review from them?
@@ -243,7 +249,7 @@ InputLabel.propTypes /* remove-proptypes */ = { | |||
/** | |||
* The variant to use. | |||
*/ | |||
variant: PropTypes.oneOf(['filled', 'outlined', 'standard']), | |||
}; | |||
variant: PropTypes.oneOf(['filled', 'outlined']), |
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.
Probably not in this PR, but we should remember to add the removal of the standard variants on the migration guide.
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.
Added it anyway for now, even though it's just copy-pasta from FilledInput
but we can reorganize the content later when there's more components ~
Co-authored-by: Diego Andai <[email protected]> Signed-off-by: Albert Yu <[email protected]>
Asked @zanivan for a review 🙏 (PS I'm planning to do the layout change involving the InputAdornment when integrating InputAdornment #39628 (comment)) |
Hey @mj12albert it looks great! Just some clarifying questions:
If so, the filled variants look good, and as I see, it matches perfectly the tokens from MD3 :) |
@zanivan Yes and yes ~ I plan to assemble only the filled I will do the changes related to the adornment in the InputAdornment PR, if I spotted this change sooner I would have done the adornment first but either way will work out ok 😬 |
Part of #38374
Closes #39512
This PR refactors
FormLabel
andInputLabel
formaterial-next
, I included both as they integrate directly together to make some visible progress on the experiments page ~material-next-filled-form-label.mov