close search

Release notes for the OpenTok.js library

Welcome to version 2.6 of the OpenTok.js library.

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

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

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


HTTPS requirement coming soon — Due to new upcoming security policies in browsers, all OpenTok-powered web applications will have to be served from secured (HTTPS) sites to access the camera and microphone. Unsecured (HTTP) sites will no longer be able to publish audio-video streams using the OpenTok platform.

Our current estimate is that these security policy changes will go into effect for Google Chrome in November 2015, with the release of Chrome 47, at the earliest. We suggest you go ahead and make the migration to reduce the chance of disruption to your application.

However, pages served over http://localhost can still access the camera and microphone (for local testing) in Chrome 47 Canary, and we assume that this will be the case in the stable version of Chrome that includes the HTTPS restriction.

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.

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 October 2, 2015 — OpenTok.js 2.6.7

Fixed issue with Firefox–Internet Explorer streaming. This release fixes issues with streams transmitted between clients using the OpenTok Plugin for Internet Explorer and Firefox version 42.

New Features on July 23, 2015 — OpenTok.js 2.6.1

This release fixes some known issues. See Fixed issues.

New Features on July 15, 2015 — OpenTok.js 2.6.0

New method for programmatically flagging an issue encountered when using OpenTok.js. See the documentation for the OT.reportIssue() method and Reporting an issue.

Support for OT.getDevices() in Internet Explorer. See the documentation for OT.getDevices() and Setting the camera and microphone used by the publisher.

Features added in previous versions

Show details.


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.

Issues subscribing to screen-sharing streams You cannot subscribe to screen-sharing streams in OpenTok.js version 2.2. To publish or subscribe to screen-sharing streams, upgrade to version 2.4.

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.

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

audioLevelUpdated events are not dispatched by the publisher in Internet Explorer.

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.

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 cannot initialize another publisher. You need to wait for the first Publisher object to dispatch the accessDialogClosed event before instantiating a second publisher.

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 using WebRTC on a page loaded from a file:// URL. You need to load the page from an http:// URL. For example, you can test a file from http://localhost if you have a web server set up on your local machine.

Fixed in OpenTok.js 2.6

Fixed in OpenTok.js 2.6.7

Issues with Firefox–Internet Explorer streaming. This release fixes issues with streams transmitted between clients using the OpenTok Plugin for Internet Explorer and Firefox version 42.

Fixed in OpenTok.js 2.6.1

OT.getDevices() returning device with the kind property set to an incorrect value. The property is set to 'audioinput' and 'videoinput' instead of 'audioInput' and 'videoInput'. We have fixed this issue.

Error running in Internet Explorer 11: Unable to get property 'split' of undefined or null reference. We have fixed this issue.

Fixed in OpenTok.js 2.6.0

Cannot read property 'videoWidth' of null Error. See this post to the OpenTok forums. We have fixed this issue.

The OpenTok plugin for Internet Explorer supports adding no more than two Subscribers to the page. We have fixed this issue.

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