Giter Site home page Giter Site logo

videojs-per-source-behaviors's Introduction

videojs-per-source-behaviors

Build Status Greenkeeper badge Slack Status

NPM

A video.js plugin for enhancing a player with behaviors related to changing media sources.

Maintenance Status: Stable

Why?

Detecting when the media source of a player has changed or is about to change is an inexact operation because the resource selection algorithm is asynchronous.

For the most part, Video.js users will be familiar with using the Player#src() method to change the source of the player. One might wonder why we don't simply trigger an event from that function to signal that the source is going to change.

The problem with that is that src() is not the only way to change the source. The underlying <video> element has multiple methods of changing the source as well and we aim to support those here.

This plugin provides events and other tools that aim to make that uncertainty a little less daunting.

Installation

npm install --save videojs-per-source-behaviors

The npm installation is preferred, but Bower works, too.

bower install  --save videojs-per-source-behaviors

Usage

To include videojs-per-source-behaviors on your website or web application, use any of the following methods.

<script> Tag

This is the simplest case. Get the script in whatever way you prefer and include the plugin after you include video.js, so that the videojs global is available.

<script src="//path/to/video.min.js"></script>
<script src="//path/to/videojs-per-source-behaviors.min.js"></script>
<script>
  var player = videojs('my-video');

  player.perSourceBehaviors();
</script>

Browserify

When using with Browserify, install videojs-per-source-behaviors via npm and require the plugin as you would any other module.

var videojs = require('video.js');

// The actual plugin function is exported by this module, but it is also
// attached to the `Player.prototype`; so, there is no need to assign it
// to a variable.
require('videojs-per-source-behaviors');

var player = videojs('my-video');

player.perSourceBehaviors();

RequireJS/AMD

When using with RequireJS (or another AMD library), get the script in whatever way you prefer and require the plugin as you normally would:

require(['video.js', 'videojs-per-source-behaviors'], function(videojs) {
  var player = videojs('my-video');

  player.perSourceBehaviors();
});

API

Once the plugin is invoked on a player - by calling player.perSourceBehaviors() - it begins firing a new event, gains two new methods, and replaces perSourceBehaviors with an object.

sourceunstable Event

The sourceunstable event will be fired when the plugin detects a condition that suggests the video player is in the process of changing sources, but that it's too early to know what the new source is or will be.

This is not a guarantee that the source will even change, but it's close - and one of the goals of this project is to continually improve this detection.

sourcechanged Event

The sourcechanged event will be fired once the call stack is cleared after the first of a subset of standard HTMLMediaElement events is encountered where the currentSrc() returned by the player has changed from the previously cached value.

previous src current src ad state triggered?
null null
null foo.mp4
null ad.mp4
foo.mp4 foo.mp4
foo.mp4 foo.mp4
foo.mp4 bar.mp4
foo.mp4 bar.mp4
foo.mp4 ad.mp4
ad.mp4 foo.mp4

Extra Event Data

An object with the following properties is passed along with sourcechanged events as the second argument to any listeners:

  • from: The source URL before the event.
  • to: The source URL after the event (and currently).
  • interimEvents: An array of all the events that occurred in the player between the event that triggered the check to the last event that fired before the call stack cleared.

Put another way, the object follows the following schema:

{
  from: <String>,
  to: <String>,
  interimEvents: [{
    time: <Number>,
    event: <Event>
  }, ...]
}

player.onPerSrc()

The onPerSrc() method has the same behavior as on() with the crucial exception that it will unbind itself if the listener is ever called with a different source than when it was bound.

Additionally, these listeners will be removed immediately before the plugin triggers a sourcechanged event. This is done because one of the core use-cases is adding new per-source listeners on the sourcechanged event and there is a chance they can double-up otherwise.

player.onePerSrc()

The onePerSrc() method has the same behavior as onPerSrc() except that it can only be called once.

player.perSourceBehaviors.disable()/player.perSourceBehaviors.enable()

These methods will disable and enable (respectively) the per-source behaviors on this player.

This is useful in more complex use-cases where you might want to manipulate the player state without triggering per-source behaviors. A good example of this might be advertising playback.

What happens when per-source behaviors are disabled?

  • The sourcechanged event will not be fired even if the source changes.
  • Any onPerSrc()/onePerSrc() listeners will not be called.
  • Binding new onPerSrc()/onePerSrc() listeners will be prevented.

player.perSourceBehaviors.disabled()/player.perSourceBehaviors.enabled()

Use these methods to inspect the current enabled/disabled state of the player as pertains to per-source behaviors. Both return a Boolean.

player.perSourceBehaviors.VERSION

Exposes the semantic version number of the plugin. This is also exposed on the plugin function (i.e. videojs.getComponent('Player').prototype.perSourceBehaviors).

License

Apache-2.0. Copyright (c) Brightcove, Inc.

videojs-per-source-behaviors's People

Contributors

alex-barstow avatar brandonocasey avatar gkatsev avatar greenkeeper[bot] avatar misteroneill avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

videojs-per-source-behaviors's Issues

An in-range update of conventional-changelog-cli is breaking the build 🚨

The devDependency conventional-changelog-cli was updated from 2.0.5 to 2.0.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

conventional-changelog-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

The devDependency rollup was updated from 0.67.3 to 0.67.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of karma is breaking the build 🚨

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.1.2

Bug Fixes

Features

Commits

The new version differs by 11 commits.

  • 7d4d347 chore: release v3.1.2
  • 5077c18 chore: update contributors
  • fb05fb1 fix(server): use flatted for json.stringify (#3220)
  • 2682bff feat(docs): callout the key debug strategies. (#3219)
  • 4e87902 fix(changelog): remove release which does not exist (#3214)
  • 30ff73b fix(browser): report errors to console during singleRun=false (#3209)
  • 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
  • dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
  • d38f344 fix(package): bump lodash version (#3203)
  • ffb41f9 refactor(browser): log state transitions in debug (#3202)
  • 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.