-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Minor UI Bugs - Playlist, Logo, and player #318
Comments
This color is automatically picked based on your accent color.
This is a issue with Vidstack & not Materialious to my understanding.
This must be a bug with Materialious and how we handle comment timestamp parsing.
Never experienced this, how often does this occur? |
After some testing with more colors, it does seem to be based off of the color picked but, it still retains a slightly different tint to everything else, is this intentional?
Interesting, if an issue isn't there already, I'll consider putting in my own.
This seems to occur fairly infrequently, but usually coincides with the player accent color bug, which itself seems uncommon, I've gotten it to trigger by refreshing a video repeatedly. EDIT: Markdown formatting. |
Yes the colors is intentional by BeerCSS yes. The player live issue always shows if a dash source is passed in Vidstack even if its set a not being a live stream. And finally the issue with refreshing video page breaking things might be due to Vidstack erroring |
Wanted to add this here, as it's also a UI bug, but for android. I figured it would be better to tack it on here, rather than making a new issue. The area around my camera that is usually the status bar is a light grey in landscape and pretty distracting. I'm not sure if the issue is isolated to my phone or not. Phone: Pixel 7 Pro (non root) Suggested Fix: Is it possible to make the bar black instead? |
Yea interesting, same issue here. I'll look into it |
Describe the bug
The following UI elements behave in sometimes odd ways:
Desktop (please complete the following information):
Additional context
To prevent spam, I thought it appropriate to merge these bugs into a single issue, if you would rather I divide any out into separate issues, please let me know.
The text was updated successfully, but these errors were encountered: