-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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: adjusted tab height #13822
fix: adjusted tab height #13822
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13822 +/- ##
==========================================
+ Coverage 76.81% 78.33% +1.52%
==========================================
Files 934 934
Lines 47249 47350 +101
Branches 5892 5948 +56
==========================================
+ Hits 36294 37092 +798
+ Misses 10808 10114 -694
+ Partials 147 144 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/testenv up |
@betodealmeida Ephemeral environment creation is currently limited to committers. |
/testenv up |
@junlincc Ephemeral environment spinning up at http://34.218.50.201:8080. Credentials are |
Thanks for the PR!
|
@junlincc hey! Thank you! I added before shots. I will happily look into that, thank you for bringing it up. |
.ant-progress-outer { | ||
${({ percent }) => !percent && `display: none;`} | ||
} | ||
.ant-progress-text { | ||
font-size: ${({ theme }) => theme.typography.sizes.s}px; | ||
} | ||
.ant-progress-bg { | ||
position: inherit; |
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.
curious, do you know specifically what this value should be? It would be better to be more explicit if you can on these three position values.
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.
no, I don't but I can test it. I think it should probably be absolute or inline-block. That's a very good point, I'll fix it tonight.
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.
@eschutho it was static!
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.
great!
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.
code lgtm. I haven't done any visual testing.
🏷 hold:testing! |
@@ -33,7 +33,8 @@ import { | |||
LOCALSTORAGE_MAX_QUERY_AGE_MS, | |||
} from '../../constants'; | |||
|
|||
const TAB_HEIGHT = 64; | |||
const TAB_HEIGHT = 90; | |||
const RESULTS_TAB_HEIGHT = TAB_HEIGHT - 10; |
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.
nice catch to make this a variable. But are they really related? Or is it just coincidence that they are 10 pixels apart? If they are separate, I would just say RESULTS_TAB_HEIGHT = 80;
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.
@eschutho I was wondering about that. Originally they were the same height, so I thought that they might be related, so that's why I had them work this way, so you only need to change one variable.
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.
Functionally they are not related though
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.
Another option is to make the tab heights the same. @Steejay what do you think about that?
@eschutho Scratch that, I checked it with the same tab height, and it looks better and is cleaner. TY |
Looks good! @Steejay if interested, here's a video. Screen.Recording.2021-04-02.at.9.25.43.AM.mov |
Ephemeral environment shutdown and build artifacts deleted. |
(cherry picked from commit 4187d9e)
SUMMARY
The scroll bar on query history disappeared based on a redesign that we did for the results page to add rows returned.
I adjusted the tab height of rows returned, in order to not have a scroll appear there, and added the scroll back to query history.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
after:
TEST PLAN
Manually checked this through docker to make sure that the portions that invoke the component work as expected.
ADDITIONAL INFORMATION