-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 button heights on commits page #3091
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3091 +/- ##
==========================================
- Coverage 33.25% 33.25% -0.01%
==========================================
Files 273 273
Lines 39954 39954
==========================================
- Hits 13288 13286 -2
- Misses 24767 24769 +2
Partials 1899 1899
Continue to review full report at Codecov.
|
LGTM |
@silverwind if this change will effect other menus? |
It will, but there should be no negative effect. You can see the override as sort of a bug fix for a bug in Semantic. |
When `.button` is not a direct descendant of `.menu` (for example, when it is wrapped), it would not get this style applied, which caused inconsistent heights of buttons that were wrapped vs. ones that weren't. Removed the `>` operator to fix this. Refs: - go-gitea/gitea#3091 - https://try.gitea.io/silverwind/testcopy/commits/branch/master
I also created Semantic-Org/Semantic-UI#5996 to fix this in Semantic itself. Thought, based on the recent activity in that repo, I don't see that one getting merged anytime soon. |
LGTM |
Fixes a issue I introduced by changing the branch button. Basically, Semantic uses the selector
.ui.menu:not(.vertical) .item > .button
which does not work if.button
is no direct child of.item
which is the case for the branch button in our case, because it's wrapped in a dropdown.Additionally, I fixed a indendation issue I introduced earlier while merging.
Before
After