-
Notifications
You must be signed in to change notification settings - Fork 51
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
Bug: React warning: maxResolution
being passed to DOM Element
#877
Comments
maxResolution
being passed to a DOM ElementmaxResolution
being passed to DOM Element
Thanks for filing the bug. We've added this feature to src={`https:stream.mux.com/${playbackId}.m3u8?max_resolution=1080p`} (See: https://docs.mux.com/guides/control-playback-resolution#specify-maximum-resolution for examples from the docs) I'll also be sure to keep you posted/update this issue if/when we get a chance to tackle this in our priority queue. |
Sounds good, thank you for the workaround! |
Is there an existing issue for this?
Which Mux Elements/Packages does this apply to? Select all that apply
mux-video-react
Which browsers are you using?
Chrome
Which operating systems are you using?
macOS
Description
This is a similar bug to #602 in that Mux video props like
maxResolution
etc are being spread to the underlying<video>
element, causing React warnings. Some props likestreamType
are being plucked out now before...rest
gets spread, but it's an incomplete list.https://github.com/muxinc/elements/blob/main/packages/mux-video-react/src/index.tsx#L27
An ideal fix would stop all props meant to only be passed as Mux media props from being spread to
<video>
so that there aren't similar future issues filed.Reduced test case
No response
Steps to reproduce
mux-video react
component withmaxResolution="1080p"
, e.g:Current Behavior
Warning logged in console
Expected Behavior
No warning logged
Errors
What version of the package are you using?
0.8.3
The text was updated successfully, but these errors were encountered: