-
Notifications
You must be signed in to change notification settings - Fork 377
fullscreen examples should have 100% height #2670
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
Conversation
|
PatternFly-React preview: https://patternfly-react-pr-2670.surge.sh |
tlabaj
left a comment
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.
LGTM
tlabaj
left a comment
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.
Do we need to update docs/website to let the consumer know?
|
Not sure, Core doesn't mention it either, perhaps we should? @mcoker |
|
@jschuler yeah, I think we should. I don't think having it in the demo is enough for a user to figure out it's required to make the page component full height. |
| code: LiveEdit, | ||
| pre: React.Fragment | ||
| pre: React.Fragment, | ||
| p: componentProps => <Text component="p" {...componentProps} />, |
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.
We (eventually) need to make sure every HTML tag is covered here that doesn't look right inside <div className="theme-pf-c-content">.
kmcfaul
left a comment
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.
lgtm
Particularly noticeable for the page demos
Closes: #1294