loading up the forgejo repo on tangled to test page performance
Fix download buttons on branches page (#30147)
Fixes https://github.com/go-gitea/gitea/issues/30143, regression from
https://github.com/go-gitea/gitea/pull/29920.
We have `.button` on the repo page, but on the branch page it's a
`.btn`. Eventually we should find a solution to have a single button
class but until then this solution should be acceptable.
(cherry picked from commit c85619b82d19a928cb219eba3f38473928b29b0c)
authored by
silverwind
and committed by
Earl Warren
8d2b7646
ea4755be
+2
-1
+1
web_src/css/modules/animations.css
+1
web_src/css/modules/animations.css
+1
-1
web_src/js/features/repo-common.js
+1
-1
web_src/js/features/repo-common.js
···
3
3
import {POST} from '../modules/fetch.js';
4
4
5
5
async function getArchive($target, url, first) {
6
-
const dropdownBtn = $target[0].closest('.ui.dropdown.button');
6
+
const dropdownBtn = $target[0].closest('.ui.dropdown.button') ?? $target[0].closest('.ui.dropdown.btn');
7
7
8
8
try {
9
9
dropdownBtn.classList.add('is-loading');