diff options
| author | 0neGal <mail@0negal.com> | 2024-02-03 19:28:09 +0100 |
|---|---|---|
| committer | 0neGal <mail@0negal.com> | 2024-02-03 19:28:09 +0100 |
| commit | 622f2289db415251073c18356c4566e0fd3c094b (patch) | |
| tree | ba40328053f27c1006743056e02756366711228f | |
| parent | 159e2f981bdbfd6a0589639424155d34b7a4cc91 (diff) | |
| download | Viper-622f2289db415251073c18356c4566e0fd3c094b.tar.gz Viper-622f2289db415251073c18356c4566e0fd3c094b.zip | |
fixed "Force quit game" button getting disabled
Due to this button (specifically the "button"/link below the "Launch"
button) serving multiple functions, it incorrectly gets disabled when
the game is running. Now its enabled!
How did I miss this? I assume it crept up after implementing the force
quit button, and not during, but maybe not, was I stupid? Mayhaps.
| -rw-r--r-- | src/app/css/theming.css | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/app/css/theming.css b/src/app/css/theming.css index d5a3d4d..aff3782 100644 --- a/src/app/css/theming.css +++ b/src/app/css/theming.css @@ -37,7 +37,7 @@ a { transition: filter 0.2s ease-in !important; } -a.disabled { +a.disabled:not("[onclick='kill_game()']") { opacity: 0.5; pointer-events: none; } |