Some CSS properties and HTML elements do not render during a co-browse session. If you are using these properties or tags an agent may not see what the consumer can see precisely during a co-browse. You should test your website to determine if your use of tags or properties cause an impact to your agent experience.
The following HTML Tags do not render during a co-browse:
HTML tag limitations
The following tags have limitations:
- Only ‘2d’ context render.
A complete set of CSS properties can be found in the W3 List of CSS properties.
The following CSS properties do not render during co-browse:
The following CSS properties have limitations:
- All backgrounds render as ‘scroll’.
- The BODY element, which renders as ‘fixed’.
- ‘content-box’ behaves the same as ‘padding-box’.
- All backgrounds are rendered as ‘padding-box’.
- All borders are rendered as ‘separate’.
- All borders are rendered as ‘solid’ or ‘none’ if you specify.
- ‘inset’ shadows do not render.
- ‘counter’ renders in Safari incorrectly.
- All cells render as ‘show’.
- Colour strings only render in Firefox, for example: linear-gradient(red,blue).
- ‘outside’ does not render.
- The following types render:
- Other types render as a ‘disc’.
- Line does not render in Chrome or Opera.
- Text renders as ‘inter-word’ in most circumstances.
- 3D transforms do not render.
Internet Explorer restrictions
When a visitor co-browses using Internet Explorer 11, the following HTML and CSS elements may not render as you expect on the agent's view:
- Use of transform:rotate
- Checkboxes using a mask property
- Creating shapes with the borders of 0 pixel page elements.
Annotations can misalign by a few pixels on Android S8+ and Pixel 2XL devices.