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

Browser window size issues #126

Closed
opened 2020年02月03日 19:41:42 +01:00 by cypherpunks · 8 comments

I have troubles using Codeberg.org due to my default privacy settings.

My screen window is 1000x600 and I'm using Tor Browser. I don't see some icons in the header (my account and + button). There is no horizontal scrollbar.

I have troubles using Codeberg.org due to my default privacy settings. My screen window is 1000x600 and I'm using Tor Browser. I don't see some icons in the header (my account and *+* button). There is no horizontal scrollbar.
Member
Copy link

If the window is becoming too small, liquid layout will move those into the burger menu ☰, click on ☰ to pull it out, just like on your phone.

If the window is becoming too small, liquid layout will move those into the burger menu ☰, click on ☰ to pull it out, just like on your phone.

I don't see it. My window isn't small enough (bug?).

I don't see it. My window isn't small enough (bug?).
Member
Copy link

Indeed, there seems to be a black hole in the liquid layout for window size 1000x600, reproducible in the responsive layout check in browser debug mode. Would you mind to report upstream to the gitea developers?

cc: @techknowlogick

Indeed, there seems to be a black hole in the liquid layout for window size 1000x600, reproducible in the responsive layout check in browser debug mode. Would you mind to report upstream to the gitea developers? cc: @techknowlogick

In standard Gitea templates this case is covered, however in the case of Codeberg there are many additional links in the header, and so you may need to customize additional components to ensure that it is covered by the above listed viewport.

In standard Gitea templates this case is covered, however in the case of Codeberg there are many additional links in the header, and so you may need to customize additional components to ensure that it is covered by the above listed viewport.
Member
Copy link

OK, thank you, we will look into this!

OK, thank you, we will look into this!

The problem still exists, even with a standard EVGA resolution of ×ばつ768.

Maybe the Codeberg links (issues, blog, join donate) could be combined into one dropdown link?

The problem still exists, even with a standard EVGA resolution of ×ばつ768. Maybe the Codeberg links (issues, blog, join donate) could be combined into one dropdown link?
Member
Copy link

CSS fix to put menu on top of buttons seems the better solution?

CSS fix to put menu on top of buttons seems the better solution?

1000x600 works now ...

1000x600 works now ...
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
5 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#126
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?