459ee98136
Thanks to inferenceus : some sort orders on the "explore/users" page could list users by their lastlogintime/updatetime. It leaks user's activity unintentionally. This PR makes that page only use "supported" sort orders. Removing the "sort orders" could also be a good solution, while IMO at the moment keeping the "create time" and "name" orders is also fine, in case some users would like to find a target user in the search result, the "sort order" might help.  (cherry picked from commit eedb8f41297c343d6073a7bab46e4df6ee297a90)
22 lines
1.3 KiB
Go HTML Template
22 lines
1.3 KiB
Go HTML Template
<div class="ui secondary filter menu gt-ac gt-mx-0">
|
|
<form class="ui form ignore-dirty gt-f1">
|
|
<div class="ui fluid action input">
|
|
{{template "shared/searchinput" dict "Value" .Keyword}}
|
|
<button class="ui primary button">{{ctx.Locale.Tr "explore.search"}}</button>
|
|
</div>
|
|
</form>
|
|
<!-- Sort -->
|
|
<div class="ui dropdown type jump item gt-mr-0">
|
|
<span class="text">
|
|
{{ctx.Locale.Tr "repo.issues.filter_sort"}}
|
|
</span>
|
|
{{svg "octicon-triangle-down" 14 "dropdown icon"}}
|
|
<div class="menu">
|
|
<a class="{{if eq .SortType "newest"}}active {{end}}item" href="{{$.Link}}?sort=newest&q={{$.Keyword}}">{{ctx.Locale.Tr "repo.issues.filter_sort.latest"}}</a>
|
|
<a class="{{if eq .SortType "oldest"}}active {{end}}item" href="{{$.Link}}?sort=oldest&q={{$.Keyword}}">{{ctx.Locale.Tr "repo.issues.filter_sort.oldest"}}</a>
|
|
<a class="{{if eq .SortType "alphabetically"}}active {{end}}item" href="{{$.Link}}?sort=alphabetically&q={{$.Keyword}}">{{ctx.Locale.Tr "repo.issues.label.filter_sort.alphabetically"}}</a>
|
|
<a class="{{if eq .SortType "reversealphabetically"}}active {{end}}item" href="{{$.Link}}?sort=reversealphabetically&q={{$.Keyword}}">{{ctx.Locale.Tr "repo.issues.label.filter_sort.reverse_alphabetically"}}</a>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div class="divider"></div>
|