Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't check "Dismiss stale approvals" nor "Ignore stale approvals" in repository branch settings #30185

Closed
yardenshoham opened this issue Mar 30, 2024 · 1 comment · Fixed by #30195
Labels
topic/ui Change the appearance of the Gitea UI type/bug

Comments

@yardenshoham
Copy link
Member

Description

Clicking these checkboxes does nothing.

Screenshots

.

Gitea Version

current main

Can you reproduce the bug on the Gitea demo site?

Yes

Operating System

No response

Browser Version

.

@yardenshoham yardenshoham added type/bug topic/ui Change the appearance of the Gitea UI labels Mar 30, 2024
@yardenshoham
Copy link
Member Author

lafriks pushed a commit that referenced this issue Mar 31, 2024
Fix #30185, regression from
#30162.

The checkboxes were unclickable because the label was positioned over
the checkbox with `padding`. Now it uses `margin` so the checkbox itself
will be clickable in all cases.

Secondly, I changed the for/id linking to also add missing `for`
attributes when `id` is present. The other way around (only `for`
present) is currently not handled and I think there are likey no
occurences in the code and introducing new non-generated `id`s might
cause problems elsewhere if we do, so I skipped on that.
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Mar 31, 2024
Fix go-gitea#30185, regression from
go-gitea#30162.

The checkboxes were unclickable because the label was positioned over
the checkbox with `padding`. Now it uses `margin` so the checkbox itself
will be clickable in all cases.

Secondly, I changed the for/id linking to also add missing `for`
attributes when `id` is present. The other way around (only `for`
present) is currently not handled and I think there are likey no
occurences in the code and introducing new non-generated `id`s might
cause problems elsewhere if we do, so I skipped on that.
silverwind added a commit that referenced this issue Mar 31, 2024
Backport #30195 by @silverwind

Fix #30185, regression from
#30162.

The checkboxes were unclickable because the label was positioned over
the checkbox with `padding`. Now it uses `margin` so the checkbox itself
will be clickable in all cases.

Secondly, I changed the for/id linking to also add missing `for`
attributes when `id` is present. The other way around (only `for`
present) is currently not handled and I think there are likey no
occurences in the code and introducing new non-generated `id`s might
cause problems elsewhere if we do, so I skipped on that.

Co-authored-by: silverwind <[email protected]>
DennisRasey pushed a commit to DennisRasey/forgejo that referenced this issue Apr 9, 2024
Fix go-gitea/gitea#30185, regression from
go-gitea/gitea#30162.

The checkboxes were unclickable because the label was positioned over
the checkbox with `padding`. Now it uses `margin` so the checkbox itself
will be clickable in all cases.

Secondly, I changed the for/id linking to also add missing `for`
attributes when `id` is present. The other way around (only `for`
present) is currently not handled and I think there are likey no
occurences in the code and introducing new non-generated `id`s might
cause problems elsewhere if we do, so I skipped on that.

(cherry picked from commit 640850e15f56bbe01f5d8ea407f99c79dc38457e)
DennisRasey pushed a commit to DennisRasey/forgejo that referenced this issue Apr 10, 2024
Backport #30195 by @silverwind

Fix go-gitea/gitea#30185, regression from
go-gitea/gitea#30162.

The checkboxes were unclickable because the label was positioned over
the checkbox with `padding`. Now it uses `margin` so the checkbox itself
will be clickable in all cases.

Secondly, I changed the for/id linking to also add missing `for`
attributes when `id` is present. The other way around (only `for`
present) is currently not handled and I think there are likey no
occurences in the code and introducing new non-generated `id`s might
cause problems elsewhere if we do, so I skipped on that.

Co-authored-by: silverwind <[email protected]>
(cherry picked from commit 9d38c4d60ef5bd015e1430386e38d9f32e050f8f)
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Jun 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/ui Change the appearance of the Gitea UI type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant