-
-
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
Code diff UI goes misalignment with code review comments #22911
Comments
Update: I proposed a draft #23096 , welcome to test & review. |
When we are releasing 1.19.1 if there is no PR to fix it. We can move it to 1.19.2 |
I think there needs a document to explain how the milestone works. In my mind, only necessary/blocker issues should be on the stable release milestones. |
Yes, we need one. I think since it has been marked bug so that it could be put in a minor version if 1.19 has been affected. |
This problem is very complicated. I don't think it could be backported easily even if it gets resolved in 1.20 |
OK. So let's move it to 1.20 |
I do think fixing this UX regression deserves some attention though. This incorrect alignment in the side-by-side diff for review comments is quite annoying. Especially for the + button to add a new review comment. Personally, I switched to the unified diff view on my company instance just to work around this issue. Does this seem like something in your wheelhouse maybe @silverwind, as you've been tackling some other UI issues related to the PR diff view lately? |
Possible, but personally I do not use side-by-side ever, so it's not a priority for me. |
Close #22911 I think it's ready for review now, feel free to test it, welcome to help to improve. ### Before ![image](https://user-images.githubusercontent.com/2114189/220958734-06871615-b498-4143-8449-3d443f08ffaa.png) ### After ![image](https://user-images.githubusercontent.com/2114189/220958621-0dce2728-57b8-4a1f-ac5d-48c7c2d42f5c.png)
Close go-gitea#22911 I think it's ready for review now, feel free to test it, welcome to help to improve. ### Before ![image](https://user-images.githubusercontent.com/2114189/220958734-06871615-b498-4143-8449-3d443f08ffaa.png) ### After ![image](https://user-images.githubusercontent.com/2114189/220958621-0dce2728-57b8-4a1f-ac5d-48c7c2d42f5c.png)
Backport #23096 by @wxiaoguang Close #22911 I think it's ready for review now, feel free to test it, welcome to help to improve. ### Before ![image](https://user-images.githubusercontent.com/2114189/220958734-06871615-b498-4143-8449-3d443f08ffaa.png) ### After ![image](https://user-images.githubusercontent.com/2114189/220958621-0dce2728-57b8-4a1f-ac5d-48c7c2d42f5c.png) Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Description
https://jsfiddle.net/ob0y2x83/
The
padding
insidetd
makes the widths oftd
become larger.The text was updated successfully, but these errors were encountered: