Codeberg/Community
54
325
Fork
You've already forked Community
12

Revert header #281

Closed
opened 2020年09月17日 23:42:05 +02:00 by TheEvilSkeleton · 16 comments

Hello, I personally dislike the new header. It's not smooth at all when refreshing and it looks like fonts that haven't been rendered.

The old header was good as is. You don't need to force yourself to look different from Gitea. In my opinion it looks worse now.

It would be better if it gets reverted.

Hello, I personally dislike the new header. It's not smooth at all when refreshing and it looks like fonts that haven't been rendered. The old header was good as is. You don't need to force yourself to look different from Gitea. In my opinion it looks worse now. It would be better if it gets reverted.

FWIW i like the new logo and somewhat more eye-friendly background color, but i dislike the font and the number of menu items.

FWIW i like the new logo and somewhat more eye-friendly background color, but i dislike the font and the number of menu items.

I have no problem with the logo as well. My problem is the header and its fonts.

I have no problem with the logo as well. My problem is the header and its fonts.

the number of menu items.

That's been there all along. In the old design, they would cover up the useful functions. I've filed an issue: #282.

> the number of menu items. That's been there all along. In the old design, they would cover up the useful functions. I've filed an issue: #282.

For what it's worth, I'm actually against this. I prefer the more compact new header.

That being said, I have no idea why it's rendering so badly in Firefox. In WebKit, it isn't too bad (see attached).

Honestly, prior to this change, Codeberg seemed to be ruining Gitea's native UI. Looks like they're turning that around :-)

For what it's worth, I'm actually against this. I prefer the more compact new header. That being said, I have no idea why it's rendering so badly in Firefox. In WebKit, it isn't too bad (see attached). Honestly, prior to this change, Codeberg seemed to be ruining Gitea's native UI. Looks like they're turning that around :-)

I think this is also a dublicate of #235

I think this is also a dublicate of #235

Not really. My complaint was the change done to the header, not about the buttons of the header not being visible.

Not really. My complaint was the change done to the header, not about the buttons of the header not being visible.
Member
Copy link

[...] It's not smooth at all when refreshing and it looks like fonts that haven't been rendered. [...]

might be a caching issue in the browser? Can you purge/reload the browser cache?

> [...] It's not smooth at all when refreshing and it looks like fonts that haven't been rendered. [...] > might be a caching issue in the browser? Can you purge/reload the browser cache?

FWIW this is on my end:

image

Where i just find the text size too big.

FWIW this is on my end: ![image](/attachments/f8581b72-5a28-4a2e-8ec9-1095b05dab5d) Where i just find the text size too big.

FWIW proposed:
image

FWIW proposed: ![image](/attachments/3140fd28-5d2a-46d5-a5dd-5ba8b6f3c79c)
Member
Copy link

FWIW this is on my end:

image

Where i just find the text size too big.

inconsistent assets in browser cache? Please purge+retry

> FWIW this is on my end: > > ![image](/attachments/f8581b72-5a28-4a2e-8ec9-1095b05dab5d) > > Where i just find the text size too big. inconsistent assets in browser cache? Please purge+retry

image

Seems to work now, thanks! ^-^

![image](https://codeberg.org/attachments/4d5f0173-6534-48b7-b3da-5abae7cf38b2) Seems to work now, thanks! ^-^

FWIW this is on my end:

image

Where i just find the text size too big.

inconsistent assets in browser cache? Please purge+retry

Unfortunately that didn't fix for me. The issue is still present.

> > FWIW this is on my end: > > > > ![image](/attachments/f8581b72-5a28-4a2e-8ec9-1095b05dab5d) > > > > Where i just find the text size too big. > > inconsistent assets in browser cache? Please purge+retry Unfortunately that didn't fix for me. The issue is still present.

Oh nice, looks like the header is back to normal(?) It looks good to me now.

Oh nice, looks like the header is back to normal(?) It looks good to me now.

Nevermind, the issue still persists. Changing links still have a weird animation

Nevermind, the issue still persists. Changing links still have a weird animation

I've submitted Codeberg/build-deploy-gitea#46

@TheMainOne There is a {grease,temper}monkey script on Codeberg/build-deploy-gitea#46 (comment) that might fix the issue for you, please try ^-^

To deploy:

  1. Install either greasemonkey or tempermonkey browser extension
  2. Disable browser cache
  3. Add the script to the extension
  4. Reload https://codeberg.org

Note that this is just a proof-of-concept for the solution in Codeberg/build-deploy-gitea#46

I've submitted https://codeberg.org/Codeberg/build-deploy-gitea/pulls/46 @TheMainOne There is a {grease,temper}monkey script on https://codeberg.org/Codeberg/build-deploy-gitea/issues/46#issuecomment-82250 that might fix the issue for you, please try ^-^ To deploy: 1. Install either greasemonkey or tempermonkey browser extension 2. Disable browser cache 3. Add the script to the extension 4. Reload https://codeberg.org Note that this is just a proof-of-concept for the solution in https://codeberg.org/Codeberg/build-deploy-gitea/pulls/46
fnetX added this to the (deleted) milestone 2021年02月27日 18:29:19 +01:00
fnetX removed this from the (deleted) milestone 2021年05月08日 22:17:36 +02:00
Owner
Copy link

Well, this is open for quite a while now. I think we won't just "revert" the header by now (so I'm closing this), but we might want to give Codeberg/build-deploy-gitea#17 a gentle push. Still on the roadmap, but the issue here is kinda confusing as it doesn't resemble the next steps any more.

Well, this is open for quite a while now. I think we won't just "revert" the header by now (so I'm closing this), but we might want to give Codeberg/build-deploy-gitea#17 a gentle push. Still on the roadmap, but the issue here is kinda confusing as it doesn't resemble the next steps any more.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 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#281
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?