-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Menu's have non-component children #3612
Comments
I am on board with the idea that we should be able to expect the contents of Probably wouldn't even need a custom component - unless it's doing something beyond what a generic component does - it could create the el and pass it as an option to a generic component. Perhaps generic components should be able to take a DOM configuration to make this easier? Something like: new Component(this, {
dom: {
tagName: 'li',
props: {},
attrs: {}
}
}); |
That does sound like a good idea IMHO :). |
Or it could be an array to match the |
Yeah that'd make even more sense I guess, then we can just pass it to that function |
Both the default menu-button (https://github.com/videojs/video.js/blob/master/src/js/menu/menu-button.js) and the chapters button (https://github.com/videojs/video.js/blob/master/src/js/control-bar/text-track-controls/chapters-button.js) (might) add a
<li>
to thechildren_
array of a menu, while I think children ofComponent
s should all be aComponent
. We can (probably) fix this by creating something like aMenuItemTitle
component.The text was updated successfully, but these errors were encountered: