Jump to: navigation, search

Co-browse Restrictions and Known Limitations

Co-browse No Longer Supports Interaction Workspace 8.1

Starting with release 8.5.0, Interaction Workspace 8.1.x is no longer supported by Genesys Co-browse.

Co-browse Must Be Deployed on the Same Second-level Domain as the Website

Due to some browsers' strict cookie policies, Genesys highly recommends that you host the Load Balancer on the same domain as the website or on one of its sub-domains. Otherwise, chat and Co-browse stickiness cookies may be rejected as third-party and the solution will not work. Users will not be able to start chat nor begin co-browsing.

Synchronization of Interactions with Browser Plugins is Not Supported

By design, synchronization of interactions with browser plugins is not supported. HTML markup managed by browser plugins (Flash, Java, Silverlight, ActiveX, etc.) is synchronized as is and may be displayed if both browsers support the plugin.

Some Obsolete Web Techniques are Not Supported

  • Quirks Mode—Co-browse requires a valid doctype. Pages in quirks mode are not supported.
  • Framesets—Obsolete technology is not supported.

Some HTML5 Features are Not Supported

The following HTML5 features are not supported:

  • Canvas
  • WebGL
  • HTML5 audio and video—HTML markup is synchronized. Synchronization of playing, pausing, etc. is not supported.


Genesys Co-browse 8.5.1 adds support for SVG in co-browse sessions.

Some Pseudo CSS Selectors are Not Supported

The following pseudo selectors are not supported:

  • :visited
  • :target
  • :active
  • :focus
  • :fullscreen
  • :scope
  • CSS3 form selectors such as :valid and :required

For other pseudo selectors (For example, :dir(), :read-only, and :nth-last-of-type()), synchronization depends on the browsers. The pseudo-selector will be synchronized only if it is supported by both browsers.

The :hover selector is supported. For more information, see JavaScript Configuration API—css.

Customer Representative Can Handle Only One Co-browse Session at a Time

Starting with Co-browse 8.5.003, an agent is by default limited to handling one co-browse session at a time. You can allow an agent to handle more than one co-browse session at a time by configuring co-browse session limitations in Workspace Desktop Edition.

Conferencing, Consultation and Transfer are Not Supported for Co-browse Sessions

As Co-browse sessions are not interactions like chat or voice, these standard operations for interactions are not currently supported for Co-browse.

Representation of Dynamically Shown List Items May be Partially Broken on Slave Browsers Using IE11

Issues may arise when IE11 is used as a slave browser on a website with dynamically shown/hidden sub-menus.




  1. Create a CSS file with a rule that sets the fixed display property of submenu list items.
    .my-submenu li {
      display: block !important;
  2. Host this file somwhere that is accessible via HTTP
  3. Specify the URL of the file in the slave.cssPatchUrl option in Config Server.

Co-browse Fails Silently on Internet Explorer 8, 9, 10

Co-browse will always fail silently when run on Internet Explorer 8, 9, or 10,, meaning that the error message Your browser is not supported will not generate.

Static resource synchronization behind authentication

Static resource synchronization is supported starting in release For information about known issues, see the Co-browser Server 9.0.x Release Note.

This page was last modified on June 25, 2019, at 11:16.


Comment on this article:

blog comments powered by Disqus