Wesley Luyten

it's because Mux player automatically loads them from the m3u8. they can be removed with some API calls to the Mux video API https://docs.mux.com/api-reference#video/operation/delete-asset-track is your intention to manually override...

thank you for reporting this! I can reproduce it, seems something in the media-control-bar is causing the overflow but I don't see what right away. edit: seems the selectmenu elements...

thanks for reminding! I repro'd again with the new player v3. it's caused by the unpositioned tooltips.

@devwilliamy is this in the iOS simulator? related https://github.com/muxinc/next-video/discussions/168

thanks for the feedback! yes, I think we're missing a few player methods that would make this easier similar to PiP https://github.com/muxinc/elements/issues/493 we'll see if we can add direct methods...

I'm running into a similar issue today w/ `playback-id` not being server side rendered in a Next.js app with https://github.com/muxinc/next-video Many other attributes are: `player-software-name="mux-player-react" player-software-version="2.0.1" style="width:640px;aspect-ratio:1.7777777777777777" data-next-video="ready" class="flex"`

this is still a bug in Chrome. filed a ticket at https://bugs.chromium.org/p/chromium/issues/detail?id=1400842#c1 reproduced at https://codesandbox.io/s/chrome-track-dynamic-cues-video-ui-bug-f1tnx2?file=/index.html

thanks for the feedback! yes, that's a good idea. it's hard to put a ETA on this, it could take a while. feel free to clone the repo and make...

this should now be quite easy to implement with something like: ```js import { CustomAudioElement } from 'custom-media-element'; import { CastableMediaMixin } from 'castable-video/castable-mixin.js'; export const CastableAudioElement = globalThis.document ?...

thanks for the quick feedback, I'll add this as a todo! normally one would show / hide the cast button with the `castchange` event like we do in Media Chrome...