Suggestions

close search

Release notes for the OpenTok.js library

Welcome to version 2.7 of the OpenTok.js library.

If you have any questions, concerns, feedback, please let us know on our forums.

Announcements
New features
Requirements
Known issues
Fixed issues
More information
How to report bugs

For details on the OpenTok.js API, see the OpenTok.js library reference.

Announcements

HTTPS requirement in Chrome — As of Chrome 47, due to new security policies, all OpenTok-powered web applications will have to be served from secured (HTTPS) sites to access the camera and microphone. Unsecured (HTTP) sites cannot publish audio-video streams using the OpenTok platform. However, pages served over http://localhost can still access the camera and microphone (for local testing).

OpenTok Plugin for Internet Explorer — The OpenTok Plugin for Internet Explorer enables OpenTok sessions in Internet Explorer. The plugin now works in Internet Explorer 9 - 11 (not supported in 64-bit mode). For information on testing your app with the OpenTok Plugin for Internet Explorer, see Developing with the OpenTok Plugin.

Discontinued support for Internet Explorer 8 — We have discontinued support for IE 8 in the OpenTok plugin for Internet Explorer.

Screen-sharing extensions for Firefox — Firefox now requires that extensions, including screen-sharing extensions for OpenTok, be signed. For more infomation, see see Developing a Firefox screen-sharing extension and this page on extension signing at mozilla.org.

Migrating from older versions — If you are moving code from version 2.0, see Migrating from OpenTok.js 2.0. If you are moving code from version 1.0, see Migrating from version 1.0 of the OpenTok JavaScript library.

New Features on November 30, 2015 — OpenTok.js 2.7.0

Suscriber stream statistics. Use the Subscriber.getStats() method to get information about the subscriber's stream quality, including the following:

To get statistics for a stream published by the local client, you must use a session that uses the OpenTok Media Router (sessions with the media mode set to routed), and you must set the testNetwork property to true in the options object you pass into the Session.subscribe() method.

The opentok-network-test repo includes sample code for showing how to use statistics of a test stream before publishing to a session.

Screen sharing support in Internet Explorer. The OpenTok plugin for Internet Explorer now supports publishing screen-sharing streams. For details, see the Screen sharing developer guide.

New new version of the Chrome screen-sharing extension. This new version, available at the screensharing-extensions repo, adds support for immediate use of the extension upon installation (without reloading the page). The OT.registerScreenSharingExtension() method now includes a version parameter to specify which version of the Chrome screen-sharing extension you are using.

New beta features. This release includes the following new beta features:

To participate in these beta programs, see the OpenTok beta programs page.

This release also fixes some known issues. See Fixed issues.

Features added in previous versions

Show details.

Requirements

The OpenTok.js library is currently supported in:

The OpenTok.js library uses port 443. Port 443 must be open on the client network.

Known issues

The following are known issues for this version of the OpenTok on WebRTC JavaScript library.

Repositioning and resizing Publisher and Subscriber elements. Do not reparent a a Publisher or Subscriber in the HTML DOM. You can reposition these elements by changing style properties. See this information on resizing and repositioning videos.

Video streaming is prevented on networks that have firewalls that use authenticated proxies. This is due to a core issue with the current underlying WebRTC implementation. (See this Chromium bug report.)

One Publisher in the OpenTok Plugin for Internet Explorer. You can only add one Publisher (within all browser windows and tabs).

Cannot hide a Publisher or Subscriber in the OpenTok Plugin for Internet Explorer. Attempting to hide the a Publisher or Subscriber (by setting style.display to "none" or visibility to "hidden") causes Internet Explorer to crash.

Issue subscribing to your own stream in Internet Explorer. In Internet Explorer, you cannot subscribe to a stream published by your own client.

The OpenTok Plugin does not support 64-bit mode in Internet Explorer. The plugin works in the 32-bit mode only.

Sessions disconnect unexpectedly in Internet Explorer 9. We have seen this issue occur occasionally if there are other clients publishing streams in the session when the client using Internet Explorer connects. If you experience this problem, please let us know at the TokBox Plugin forum. (Please provide details, including the version of Windows, the version of Internet Explorer, the version of the Plugin, the URL of the app, and what was led up to the session disconnecting. You can get the version of the plugin by entering TBPlugin.version() in the console.)

Issue updating the OpenTok Plugin for Internet Explorer. When updating older versions of the OpenTok plug-in for Internet Explorer (prior to 2.6.0), users will be asked to install a new plug-in (instead of update). Installing the new plug-in will cause the update to take effect

Issues setting video source for a Publisher in Firefox. In an page loaded via HTTPS, if the user clicks "Always Share" when granting access to the camera, you can only use that camera. You cannot set the video source to another camera.

The OpenTok plugin for Internet Explorer does not work in sandboxed iframes. This is an intentional limitation of the browser. The browser blocks plugin content inside a sandboxed frame.

WebRTC is a peer-to-peer protocol, and it is possible that connections will fail to connect. The most common cause for failure is a firewall that the protocol cannot traverse. When OpenTok detects this failure, the TB object dispatches an exception event object, with the code property set to 1013.

You cannot publish video on a page loaded from a file:// URL, due to browser security limitations. You need to load the page from an http:// or https:// URL. Note also, that Chrome requires you to load a page from an https:// URL (although you can use http to test a localhost URL in Chrome). For example, you can test a page from http://localhost if you have a web server set up on your local machine.

Fixed in OpenTok.js 2.7

Fixed in OpenTok.js 2.7.2

Publisher accessDenied event not working in Firefox 44. We have fixed this issue.

Error when subscribing to the same stream multiple times. We have fixed this issue.

Fixed in OpenTok.js 2.7.1

Subscribing to you own stream (using the testNetwork option in the Session.subscribe() method) is not working in Chrome. We have fixed this issue.

global.jasmine property set. The OpenTok.js library was incorrectly adding this property. We have fixed this issue.

Error logged in console: "More than one module is trying to define on on OTHelpers." We have fixed this issue.

Fixed in OpenTok.js 2.7.0

audioLevelUpdated events are not dispatched by the Publisher in Internet Explorer. We have fixed this issue.

OT.initPublisher() fails if the Allow Device Access dialog box is open for another Publisher. This problem occured in Firefox and Internet Explorer. We have fixed this issue.

videoDisabledDisplayMode style working incorrectly. This is an optional property you pass into the style property of the Session.subscribe() options parameter or using the Subscriber.setStyle() method. We have fixed this issue.

Unable to publish or subscribe in Firefox 43+. This is due to a change in the WebRTC API implemented in Firefox. We have fixed this issue.

Unable to initialize two publishers synchronously in Firefox and Internet Explorer. In Firefox and the OpenTok Plugin for Internet Explorer, while the user is being prompted to grant a publisher access to the camera and microphone, you could not initialize another publisher. We have fixed this issue.

Added support for screen sharing in Internet Explorer.

Fixed in previous versions

Show details.

More information

See the reference documentation for the OpenTok.js library.

To see sample code and to read more information on using the OpenTok.js library, see the OpenTok Tutorials and Examples page.

For documentation on the OpenTok server-side libraries, see the OpenTok server-side libraries page.

Also check out the OpenTok Help Center.

How to report bugs

We'd love to hear from you! If you have any issues or bugs, you can report them to us at support@tokbox.com.