Github logo not visible in the login page #1023

Closed
opened 2023-05-14 11:37:21 +02:00 by mehrad · 9 comments
Image

I just realized that the new nice dark theme of Codeberg has cause the Github logo to be practically invisible. In the screenshot below, I am comparing the current Codeberg vs. the Gitea demo:

image


I suggest #1d394a for the div to follow the blue style of Codeberg, and also improve visibility

image

I just realized that the new nice dark theme of Codeberg has cause the Github logo to be practically invisible. In the screenshot below, I am comparing the current Codeberg vs. the Gitea demo: ![image](/attachments/5e48eded-0e62-4953-83b1-f12a6fe74f39) ------- I suggest `#1d394a` for the div to follow the blue style of Codeberg, and also improve visibility ![image](/attachments/f348b601-c667-4e1e-9e9c-25d7fbf98394)
100 KiB
100 KiB
Image
Will be fixed with https://github.com/go-gitea/gitea/pull/24740
Image
Owner

AWESOME JOB!!!!!!! Thank you for your efforts! @silverwind

AWESOME JOB!!!!!!! Thank you for your efforts! @silverwind
Image
Owner

Is a duplicate of #917, deliberately not closing as this is where the discussion / updates seem to be happening and is cross-linked from the Gitea PR.

Is a duplicate of https://codeberg.org/Codeberg/Community/issues/917, deliberately not closing as this is where the discussion / updates seem to be happening and is cross-linked from the Gitea PR.
Image
Member

I am not in favor of keeping duplicate issues open in spite of the discussion that has taken place here, it'll just increase the odds that one of them gets missed when the fix is downstreamed and will sit cluttering the issue tracker.

I am not in favor of keeping duplicate issues open in spite of the discussion that has taken place here, it'll just increase the odds that one of them gets missed when the fix is downstreamed and will sit cluttering the issue tracker.
Image
Owner

This case was treated as an exception (possibly wouldn't have happened if duplicate issue was closed fast enough, but on the other hand, this may not have been resolved if the Gitea maintainer here had missed the other issue) and I tried to communicate that well enough so as to not bother an external participant in the conversation for the first time, was hoping that a big deal wouldn't be made out of it as I hoped that my intentions would've been obvious enough so as to not have to justify them.

I had no plans to do this again in the future.

PR merged in https://github.com/go-gitea/gitea/pull/24740, keeping both issues open until it lands in Codeberg.

This case was treated as an exception (possibly wouldn't have happened if duplicate issue was closed fast enough, but on the other hand, this may not have been resolved if the Gitea maintainer here had missed the other issue) and I tried to communicate that well enough so as to not bother an external participant in the conversation for the first time, was hoping that a big deal wouldn't be made out of it as I hoped that my intentions would've been obvious enough so as to not have to justify them. I had no plans to do this again in the future. PR merged in https://github.com/go-gitea/gitea/pull/24740, keeping both issues open until it lands in Codeberg.
Image
Author

Thanks for point out that this is potentially a duplicate. As far as I can tell, this is not a duplicate although both point at the same direction. To clarify my rational, the #917 points at changing the icon and the suggestion is a neon icon for github. This thread is directly aiming at a simple CSS change of the surrounding box.

These said, the #917 did not show up in any of my searches neither in Codeberg issue not gitea, most probably because of bad formatting of the text and title. Perhaps this is why the gitea maintainer also missed that one as well. I myself am a maintainer of some git repos, and I sometimes have to modify the title to make it more specific to the issue at hand and avoid duplicates.

Again, I apologize for potential duplicate, but it practically cannot be avoided if it does not show up as a potential hit in any of the searches.

Thanks for point out that this is potentially a duplicate. As far as I can tell, this is not a duplicate although both point at the same direction. To clarify my rational, the #917 points at changing the icon and the suggestion is a neon icon for github. This thread is directly aiming at a simple CSS change of the surrounding box. These said, the #917 did not show up in any of my searches neither in Codeberg issue not gitea, most probably because of bad formatting of the text and title. Perhaps this is why the gitea maintainer also missed that one as well. I myself am a maintainer of some git repos, and I sometimes have to modify the title to make it more specific to the issue at hand and avoid duplicates. Again, I apologize for potential duplicate, but it practically cannot be avoided if it does not show up as a potential hit in any of the searches.
Image
Owner

Hey @mehrad, I believe that this issue has been fixed with the latest update that was installed today (v1.20). If I'm wrong, please don't hesitate to reopen this issue.

Hey @mehrad, I believe that this issue has been fixed with the latest update that was installed today (v1.20). If I'm wrong, please don't hesitate to reopen this issue.
Image
Author

I agree, the current state looks slick and nice. Thanks.

I agree, the current state looks slick and nice. Thanks.
Image
Owner

Thank silverwind, and thank you for reporting this!

Thank silverwind, and thank you for reporting this!
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1023
No description provided.