-
Notifications
You must be signed in to change notification settings - Fork 843
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
Flyout alterations #925
Flyout alterations #925
Conversation
- Added “cross” close button to top right as default if (“onClose”) is present - Added option for a border below header - Altered doc examples to represent how we _want_ the flyouts to display consistently
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! pulled code and ran through the examples; tested escape-key functionality still works when hiding the close button.
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.
This looks great. Thanks for picking it up.
Don't forget the changelog before you merge. Because people were adding these on their own, and the default ability will add them (which makes sense) we should prolly add some sort of warning in the changelog more than usual. It's not a breaking change, but people should be aware to remove their additive stuff.
/** | ||
* Locks the mouse / keyboard focus to within the flyout | ||
*/ | ||
ownFocus: PropTypes.bool, | ||
}; | ||
|
||
EuiFlyout.defaultProps = { |
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 default bool props - changelog
cc @ycombinator, @justinkambic. I noticed you were adding these close buttons manually in the Pipeline viewer. We're just going to make it a default EUI behavior. When this merges down into Kibana, you'll want to remove your additional buttons so that we don't have duplicate functionality. |
@snide Thanks for the heads up. BTW, grepping through the Kibana code it looks like there are manually-added close buttons in quite a few other places too. I'm not sure how all those other places of |
The close buttons in the footer should be fine. Generally they shouldn't need them anymore, but they won't visually "break" things. |
@snide I made some design decisions on the header, let me know if you think otherwise.