There are tags displaying on the tags page which aren’t appearing in the tags dropdown or search.
One example (of many) here on Meta is #bug::tag
There are tags displaying on the tags page which aren’t appearing in the tags dropdown or search.
One example (of many) here on Meta is #bug::tag
This is because of site setting max tags in filter list
which defaults to 30. The description of the site setting is:
Maximum number of tags to show in the filter dropdown. The most used tags will be shown.
I just increased that setting to 100
here on Meta and #bug::tag is appearing in dropdown now.
If that is the case, this is not a bug @hawk.
what we could do though is making this component make ajax request if filtering doesnt return anything. Or apply filtering on the full list even if we only show a partial list in the first place.
I’d favor this solution: users usually don’t know about the max tags
limit, and would expect they search the complete tag set when entering anything into the Search… field.
Is this still the case? We should at least hint at the existence of more tags at the bottom with more … or similar.
@codinghorror long time ago I implemented this:
It is however true, that you have to filter to find it, and nothing hints you that there are more than the displayed list. Do you still want to implement more… ?
Yes – I think there should be some kind of visual hint that “ah, there is more here, not just the visible items”… whatever is easy.
On second thought, I don’t think I can do this, at least not with a perf hit.
If we limit the tags displayed it’s basically to not have to fetch (or even count) all tags. So the only thing I know is if we have less displayed tags than the max setting, but I have no way to know if we have more tags than the max displayed, because in this case: displayed === max.
A trick I commonly use, have the backend always return max+1 rows, only display max. If +1 exists you have more.
That is… One Weird Old Trick™