-
Notifications
You must be signed in to change notification settings - Fork 227
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
fix(top-app-bar): allow react elements in title #376
Conversation
Codecov Report
@@ Coverage Diff @@
## master #376 +/- ##
=======================================
Coverage 96.92% 96.92%
=======================================
Files 51 51
Lines 1823 1823
Branches 211 211
=======================================
Hits 1767 1767
Misses 56 56
Continue to review full report at Codecov.
|
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.
Putting a node as label
for Text Field messes up its positioning... I'm guessing this has to do with the MDC Web calculations around the width/position/size of the label. I'd suggest we keep this PR for Top App Bar and file a separate bug for allowing node prop in Text Field
created #388 |
…ial-components-web-react into fix/list/allow-alternate-tags * 'master' of https://github.com/material-components/material-components-web-react: docs(menu-surface): open state & ref errors (material-components#412) fix(text-field): allow for input isValid override (material-components#374) feat(list): Add List Group and List Group Subheader (material-components#386) fix(top-app-bar): allow react elements in title (material-components#376) docs: update main component manifest on main Readme (material-components#394) docs: update roadmap (material-components#396) docs: Add web survey link in readmes (material-components#402) docs: update main README with CRA2 guidelines (material-components#393)
fixes #253