Archived label visual bug in labels select

[stuzer05]

Description

When you have archived non-exclusive label between exclusive label groups the double divider is shown in the place of archived label

Gitea Version

trunk

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

None

[neel1996]

The issue is due to the divider being rendered unconditionally

This has been fixed as part of #27668

[delvh]

I think the easiest approach to completely fix the problem is by refactoring the code completely.
As far as I know, @puni9869 is already working on sorting archived labels to the bottom of the search results, which will fix this problem as well and it will be much less error-prone.

[puni9869]

The issue is due to the divider being rendered unconditionally

This has been fixed as part of #27668

This is known issue.

[wxiaoguang]

Does the problem still exist in 1.23?

[stuzer05]

Does the problem still exist in 1.23?

It does

Gitea 6bd70d4

[stuzer05]

repo labels
org labels

[wxiaoguang]

The problem is that tw-hidden doesn't work with the dropdown divider. It can't be fixed by template patches.

[stuzer05]

The problem is that tw-hidden doesn't work with the dropdown divider. It can't be fixed by template patches.

I don't know how labels work currently, but I'd imagine backend would for a merged list of labels aka. map[map[int64, string]] and frontend would just print that nested grouped map. With this logic, but would never happen

[wxiaoguang]

The problem is that tw-hidden doesn't work with the dropdown divider. It can't be fixed by template patches.

I don't know how labels work currently, but I'd imagine backend would for a merged list of labels aka. map[map[int64, string]] and frontend would just print that nested grouped map. With this logic, but would never happen

It's not that easy. Frontend dropdown needs to "filter" the list. So it also needs to handle such case:

item1
divider
item2 (not matched the input and will be hidden by frontend)
divider (this will also be hidden)
item3

Actually the dropdown could already handles such case, but it is unable to mix these 2 different usages if item2 is hidden by other methods but not by the filter.

[stuzer05]

if item2 is hidden by other methods

Shouldn't those items that are hidden by other methods be non-existent for dropdown? Where am I missing?