-
Notifications
You must be signed in to change notification settings - Fork 13k
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
css: add margin-top to ResultSet #7679
Conversation
@@ -73,6 +73,7 @@ export default class ResultSet extends React.PureComponent { | |||
// when new results comes in, save them locally and clear in store | |||
if (this.props.cache && (!nextProps.query.cached) | |||
&& nextProps.query.results | |||
&& nextProps.query.results.data |
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.
FYI: Unrelated bug I hit while doing CSS tweaks
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
I'm curious about the structure here and if there's a reason why we wouldn't just want to add padding to the tab-pane
div by default so that each possible child element wouldn't need to have a margin. Does it not play nicely with the table elements?
I thought about the tradeoffs of padding the tab-pane a little, and though maybe we wanted more density like for data tables/previews. Then I thought that we don't want left or right margins for the layout to align. I can to the conclusion that it's for the children to decide how they want to use the space. I'm no designer and don't know much about structuring CSS properly. Happy to take a different approach. |
That makes sense to me, thanks for the context! |
(cherry picked from commit f278faa)
(cherry picked from commit f278faa)
CATEGORY
Choose one
SUMMARY
See images
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before
After