-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 pull request commit list item positions #12382
Conversation
Is there an example of this on try.gitea.io? Clearfix seems so oldschool, I wonder of there are better solutions. |
looks like this happens because of |
It gets better with signed commits 😂 |
@jolheiser actually this looks like so artistic. maybe we should NOT fix this 😜 |
Chrome 84.0.4147.105 (64 bit) / Windows 10 |
Weird, Chrome 84.0.4147.105 on macOS renders it fine. Such issues are usually not platform-specific. |
Interesting -- can't reproduce this either on macOS in any browser |
Have you customerized your gitea's css? |
Something interesting to note, checking now on my Linux machine, same browser as before (Brave), it looks just fine. |
@lunny i did not customize gitea's css. i can reproduce also in try this should be chrome's issue for windows build. because there is one more thing https://gitea.com/gitea/changelog/pulls/44 |
I can try on Windows later but ultimately I think we should flexbox these timeline messages instead of adding extending the float hacks further. |
@silverwind I dont know best practices for |
Basically you want a horizontal flexbox with spacing between, e.g. <div class="timeline-entry">
<div class="timeline-entry-left"></div>
<div class="timeline-entry-right"></div>
</div> .timeline-entry {
display: flex;
justify-content: space-between;
align-items: center;
}
.timeline-entry-left,
.timeline-entry-right {
display: flex;
align-items: center;
} This should give a basic layout that works. Margins will need to be added because inside a flexbox, HTML whitespace is not significant. CSS-based text truncation may be needed on the left element. Or if the server already truncates, that's fine too. |
Can not reproduce on Chromium 84.0.4147.89 on Windows |
@CirnoT this should be new in Chrome 84.0.4147.105 |
Maybe report it to https://bugs.chromium.org/p/chromium/issues. |
Just to say I can't reproduce on: Chrome linux 84.0.4147.105 (Official Build) (64-bit) |
If no one can reproduce, maybe it's a extension or something interferring? Tried a clean browser profile yet? |
I tried on clean browser. Is there anyone using windows 10 google chrome 84.0.4147.105 |
Just tried that exact browser/os and still cannot reproduce. |
@silverwind i have 2 laptops. I can reproduce on both |
@jaqra |
Interestingly this looks solved. This is not broken now But commit positions is still broken Feel free to close this pr if no one can reproduce |
The misaligned reactions may be an effect of #12317 but I did not observe it. It certainly made them a bit smaller (1.25em vs previous 1.5em) |
@silverwind this screenshots are from gitea.com. yesterday and today. i guess gitea.com did not upgrade |
gitea.com is at e67c04251 so should have that PR. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions. |
This has started happening for me recently, don't really feel like bisecting which commit broke it explicitly, but the actual reason for this happening is that the spacing between two |
This should have been resolved. |
looks problem resolved. i am closing this |
I dont know if there is issue related this
Before
After