Can't set collaborator permissions with only keyboard #4094

New Issue

GiteaMirror · 2025-11-02T05:37:35-06:00

GiteaMirror commented

2025-11-02 05:37:35 -06:00

Originally created by @Jookia on GitHub (Oct 11, 2019).

Gitea version (or commit ref): 1.9.1
Git version: 2.23
Operating system: Arch Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
  https://try.gitea.io/Jookia/test/settings/collaboration
- No
- Not relevant
Log gist:

Description

When managing collaborators in repository settings, any changes to user permissions made just by using the keyboard to focus the drop down menu and arrows to select an item do not save. I looked at the HTML and saw that the saving only happens onclick, which isn't triggered when using the keyboard.

Because of this you can't set collaborator permissions with only the keyboard. This is a significant roadblock for accessibility.

Screenshots

Bug isn't visible in a screenshot

Originally created by @Jookia on GitHub (Oct 11, 2019). - Gitea version (or commit ref): 1.9.1 - Git version: 2.23 - Operating system: Arch Linux - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://try.gitea.io/Jookia/test/settings/collaboration - [ ] No - [ ] Not relevant - Log gist: ## Description When managing collaborators in repository settings, any changes to user permissions made just by using the keyboard to focus the drop down menu and arrows to select an item do not save. I looked at the HTML and saw that the saving only happens onclick, which isn't triggered when using the keyboard. Because of this you can't set collaborator permissions with only the keyboard. This is a significant roadblock for accessibility. ## Screenshots Bug isn't visible in a screenshot

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 05:37:35 -06:00

GiteaMirror closed this issue

2025-11-02 05:37:35 -06:00

GiteaMirror commented

2025-11-02 05:37:36 -06:00

@stale[bot] commented on GitHub (Dec 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:37:37 -06:00

@zeripath commented on GitHub (Dec 10, 2019):

Is this still the case?

@zeripath commented on GitHub (Dec 10, 2019): Is this still the case?

GiteaMirror commented

2025-11-02 05:37:37 -06:00

@Jookia commented on GitHub (Dec 11, 2019):

Yes, I haven't written the rest of the dropdown menu accessibility code as I've been doing other things. I needed to do an audit of the dropdown menus in HTML for a reason I forget- I think so I could test all of them. I'll try having a shot at this sometime this month.

@Jookia commented on GitHub (Dec 11, 2019): Yes, I haven't written the rest of the dropdown menu accessibility code as I've been doing other things. I needed to do an audit of the dropdown menus in HTML for a reason I forget- I think so I could test all of them. I'll try having a shot at this sometime this month.

GiteaMirror commented

2025-11-02 05:37:37 -06:00

@stale[bot] commented on GitHub (Feb 9, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 9, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:37:38 -06:00

@fsologureng commented on GitHub (Nov 28, 2022):

I think this issue is resolved. At least I could added @jookia as a collaborator in my test repo and set them permissions with just keyboard interaction.

@fsologureng commented on GitHub (Nov 28, 2022): I think this issue is resolved. At least I could added @jookia as a collaborator in my test repo and set them permissions with just keyboard interaction.

GiteaMirror commented

2025-11-02 05:37:38 -06:00

@wxiaoguang commented on GitHub (Nov 29, 2022):

Fixed by https://github.com/go-gitea/gitea/pull/19861#issuecomment-1143576632 and confirmed by Jookia: https://github.com/go-gitea/gitea/pull/19861#issuecomment-1144781891

I will close this issue.

@wxiaoguang commented on GitHub (Nov 29, 2022): Fixed by https://github.com/go-gitea/gitea/pull/19861#issuecomment-1143576632 and confirmed by Jookia: https://github.com/go-gitea/gitea/pull/19861#issuecomment-1144781891 I will close this issue.

GiteaMirror referenced this issue

2025-11-02 12:30:38 -06:00

[PR #4101] [MERGED] Add how-to for enabling HTTPS #17243

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#4094