Avoid thin splitter #16
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
February 20, 2016 11:39
Previously these were separated via a 1px wide splitter. This had two issues: * By default, headers would expand and cover body up. * 1px was *very* hard to click+drag on, making it a pretty painful experience to expand either panel. This keeps this tidier, and more consistent with the rest of the layout.
This makes it easy to point at and drag around.
|
Bump? |
3 similar comments
|
Bump? |
|
Bump? |
|
Bump? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The very very thing splitter that separates panels (body/headers and also request/history) has always annoyed me. It's extremely thin, and it usually takes me a few tens of seconds to pinpoint correctly and drag around (I can't image somebody with actual motor problems!).
I've worked around this by:
Replace the body/headers splitter with a tabset. This also looks tidier and is a bit more consistent with the rest of the layout:
Before:
After:
I also made the splitter that separates the request from the history panels 3px high, which makes it a lot easier to click/drag.