Skip to content
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

Removed the passing of playerOptions to plugins #2532

Closed
wants to merge 1 commit into from

Conversation

heff
Copy link
Member

@heff heff commented Sep 1, 2015

...because it caused an error, and it actually creates an inconsistent
plugin init process, when considering plugins that are initialized
outside of the player init.

fixes #2510

This was originally introduced in #2229, by my request. Seemed like a good idea at the time but unless anyone thinks it would be very valuable I think we should remove it for the consistency reason mentioned.

Also changed the Plugin var name in tests for clarity, before deciding just to remove the feature.

...because it caused an error, and it actually creates an inconsistent
plugin init process, when considering plugins that are initialized
outside of the player init.

fixes videojs#2510
@@ -157,7 +157,6 @@ class Player extends Component {
let plugins = options.plugins;

Object.getOwnPropertyNames(plugins).forEach(function(name){
plugins[name].playerOptions = playerOptionsCopy;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only interesting change.

@gkatsev
Copy link
Member

gkatsev commented Sep 2, 2015

Sounds good to me.

@mmcc
Copy link
Member

mmcc commented Sep 2, 2015

lgtm as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to initialize plugins via options
3 participants