-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI uses last service colours instead of current service used #9632
Comments
The colour is an indication of which service is currently active within the app for the purpose of searching, and accessing kiosks. Users would be confused if they finished watching/listening to something from an external link, and then tried to search for something, but found that the search results were from a completely different service than what the colour indicated. |
What if the colour shown on the media page was always that of where the media is taken from, but the active kiosk stays the same so that other pages (like the search page) keep the colour of the active kiosk ? Or even: what if the active kiosk changes upon viewing/listenning a media page ? This way the colour scheme would still match the active kiosk and the user wouldn't be lost in another kiosk when using the search feuture upon leaving the media page. |
It would become quite annoying if the service kept changing with every link you opened.
This sounds like a viable option. |
Idk it doesn't happen too much time in my use case. Most of the time i'm switching between 2 kiosks (bandcamp and youtube, for music) when i'm searching for something. |
Checklist
Affected version
0.24.1
Steps to reproduce the bug
Expected behavior
The UI should probably bear the colours of the website the media i'm opening is from.
Actual behavior
The UI is now blue instead of red, and the app still thinks i'm using Bandcamp
Screenshots/Screen recordings
Logs
No response
Affected Android/Custom ROM version
Android 11
Affected device model
Nokia TA-1157
Additional information
No response
The text was updated successfully, but these errors were encountered: