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

Can I know where the Sign-out Button is? #192

Closed
opened 2020年06月14日 10:16:59 +02:00 by phtan · 12 comments

To reproduce:

  • Sign into Codeberg/Gitea
  • Attempt to sign out

Problem:

I expected to see a button to allow me to sign out. I have not managed to find it so far. Maybe someone else knows better than me?

**To reproduce:** - Sign into Codeberg/Gitea - Attempt to sign out **Problem:** I expected to see a button to allow me to sign out. I have not managed to find it so far. Maybe someone else knows better than me?
Member
Copy link

top-right menu, last menu item (bottom) -> sign out.

top-right menu, last menu item (bottom) -> sign out.

A picture says it best.

A picture says it best.

Maybe @phtan has that horizontal resolution where the button is not visible...

Maybe @phtan has that horizontal resolution where the button is not visible...
Author
Copy link

Thanks @hw , @Masgalor and @ashimokawa for your responses.

I attach a screen-shot.

My Display Resolution is apparently 1920 x 1080.

Thanks @hw , @Masgalor and @ashimokawa for your responses. I attach a screen-shot. My Display Resolution is apparently 1920 x 1080.
Author
Copy link

I have temporarily found a resolution (pun intended) for this issue.

In Windows' Display Settings, I can change a setting called Scale, from the default 150% to 100%. (Please see screen-shots).

Then, in my Web-browser, at codeberg.org, I can see the option to Sign Out, and other options.

This is the first time that I have changed - or am even aware that there is - a Scale setting, so thanks for your patience.

However, it remains to be seen whether I can adjust to this new display on my computer.

Let me know if you want me to close this issue - it is not exactly clear to me if Codeberg-Gitea should accommodate my display preferences, or if my display preferences have to accommodate Codeberg-Gitea. (I have had no issues with other web-sites, at 150% scale of display, as far as I am aware - in the past 2.5 years or so).

I have temporarily found a resolution (pun intended) for this issue. In Windows' Display Settings, I can change a setting called Scale, from the default 150% to 100%. (Please see screen-shots). Then, in my Web-browser, at codeberg.org, I can see the option to Sign Out, and other options. This is the first time that I have changed - or am even aware that there is - a Scale setting, so thanks for your patience. However, it remains to be seen whether I can adjust to this new display on my computer. Let me know if you want me to close this issue - it is not exactly clear to me if Codeberg-Gitea should accommodate my display preferences, or if my display preferences have to accommodate Codeberg-Gitea. (I have had no issues with other web-sites, at 150% scale of display, as far as I am aware - in the past 2.5 years or so).

In Windows’ Display Settings, I can change a setting called Scale, from the default 150% to 100%. (Please see screen-shots).

Just as a side note, you can set a zoom level inside your browser.
Either in the page settings or by scrolling your mouse wheel while holding down the ctrl-button. No need to mess up your system settings.

Let me know if you want me to close this issue - it is not exactly clear to me if Codeberg-Gitea should accommodate my display preferences, or if my display preferences have to accommodate Codeberg-Gitea.

The site should be usable regardless your displys preferences.
If your horizontal resolution gets too small the navbar switches to a one button dropdown-menu. Thats for mobile usage in the first place, but something like that should happen if not all elements in the navbar are visible.

Unfortunately, I dont know anything about CSS stuff so I cant have a look at it.

> In Windows’ Display Settings, I can change a setting called Scale, from the default 150% to 100%. (Please see screen-shots). Just as a side note, you can set a zoom level inside your browser. Either in the page settings or by scrolling your mouse wheel while holding down the ctrl-button. No need to mess up your system settings. > Let me know if you want me to close this issue - it is not exactly clear to me if Codeberg-Gitea should accommodate my display preferences, or if my display preferences have to accommodate Codeberg-Gitea. The site should be usable regardless your displys preferences. If your horizontal resolution gets too small the navbar switches to a one button dropdown-menu. Thats for mobile usage in the first place, but something like that should happen if not all elements in the navbar are visible. Unfortunately, I dont know anything about CSS stuff so I cant have a look at it.

Turns out there is already an open issue for this kind of problem. #126

Turns out there is already an open issue for this kind of problem. #126
Member
Copy link

Indeed, this needs a fix.

Indeed, this needs a fix.
Author
Copy link

Just as a side note, you can set a zoom level inside your browser

Well-noted and appreciated, @Masgalor

Turns out there is already an open issue for this kind of problem.

Interesting...

> Just as a side note, you can set a zoom level inside your browser Well-noted and appreciated, @Masgalor > Turns out there is already an open issue for this kind of problem. Interesting...

As an easy fix, this would only require a few changes to the CSS files. Increasing the min-/max-width from 767/768 px to something like 1267/1268 px as limit for switching to burger menu.

Should the changes be put into https://codeberg.org/Codeberg/build-deploy-gitea/src/branch/master/etc/gitea/public/codeberg.css or rather be done inside https://codeberg.org/Codeberg/gitea/src/branch/codeberg/web_src/less?

As an easy fix, this would only require a few changes to the CSS files. Increasing the min-/max-width from 767/768 px to something like 1267/1268 px as limit for switching to burger menu. Should the changes be put into https://codeberg.org/Codeberg/build-deploy-gitea/src/branch/master/etc/gitea/public/codeberg.css or rather be done inside https://codeberg.org/Codeberg/gitea/src/branch/codeberg/web_src/less?
Member
Copy link

If possible, to codeberg.css.

If possible, to `codeberg.css`.
Owner
Copy link

Still valid, but already tracked in #235

Still valid, but already tracked in #235
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#192
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?