-
Notifications
You must be signed in to change notification settings - Fork 90
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
fix: revert theme render flicker (breakpoints) #1055
Conversation
@luwes is attempting to deploy a commit to the Mux Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cca3a3a
to
2b00da2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1055 +/- ##
==========================================
- Coverage 78.55% 77.48% -1.07%
==========================================
Files 59 51 -8
Lines 11080 12313 +1233
Branches 0 722 +722
==========================================
+ Hits 8704 9541 +837
- Misses 2376 2744 +368
- Partials 0 28 +28 ☔ View full report in Codecov by Sentry. |
related muxinc/media-chrome#1055 this should fix the flicker that could happen between showing the thumbnail and showing the whole theme w/ thumbnail. - [x] todo: double check removing that hide not defined CSS doesn't cause glitches
related #960
from feedback via next-video we heard there is a split second empty flicker now when using a slotted poster image.
first the blurhash appears, after the thumbnail then nothing (seeing background of page), then the poster and player UI.
the reason is that the theme visibility is hidden until the breakpoints are available.
after reconsideration this solution doesn't feel like the correct way to handle this.
better is to be more precise in the theme itself and require breakpoints to render any control variants.
this will require some changes in some themes where we don't default to the smallest size variant for example but still require a small breakpoint width. could be even zero.