This feature is available since 2.16v
In chat window click eye icon
As soon you click this icon you will see window similar to this one. If you have not enabled automatic screen sharing acceptance from user you have to click blue eye first.
Red eye - if you move your mouse over it will tell at what status screen sharing window is. If you do not see message click to share a screen, that means we are pending actions from user. As soon you click blue eye user will be promted to grant permission to see his screen.
Mouse checkbox - if you check this options. Your mouse position will be shared with user mouse position
Window checkbox - if you check this as soon you highligh some element by clicking on element on page user screen will be scorel to that element
Network icon - if you click this icon you can navigate user precisely to any page you want
As soon user agrees to do that you will see user screen. Then user terminates Co-Browsing your Co-Browsing window content will be cleared.
This can be done at
You have to check "Do not ask permission for users to see their screen" so as soon you open Co-Browsing window and click blue eye user screen will be shared without his permission. In any case user will be able to terminate this by clicking blue box at the top right of the screen.
There is around 5-7 seconds delay untill roundtrip. So just have to be patient
If you are using NodeJs roundtrip should take about 3-5 seconds. Just play around yourself so you will see how fast it navigates in your site.
Yes since 2.18v. Operator Co-Browsing window will represent live form values changes. So basically
Then you move mouse over menu in operator window, these actions are not synced to user computer. Dropped menu will allow you easily navigate user to desirable window.
No. It's browse security stuff and only main window is synced, it's just technically not possible. Prove me wrong! :)
Mutation summary does not track these kinda data. Only DOM changes are synced. Forms changes tracking was done by me. Mutation summary also did not had sutch capability.
There is the only one tricky part. Browser forbids downloading insecure content if site is in http mode and lhc itself in https. We deal with this limitation by proxying CSS request through LHC itself. That way we support all possible cobinations http -> https, https -> https, http -> http. In any case i recommend to use same protocol for site and lhc itself.
The biggest advantage for using NodeJs for Co-Browsing mode is the updates speed. In ajax mode there is some delay before user screen changes is transmited to operator window. With NodeJs these changes are transmitted instantly. You will be able to see almoust live user mouse movements.
NodeJs server is located at doc/node_servers/cobrowsing
Just read readme.txt file content from there also do not forget to enable it in livehelper chat in chat configuration section.
Developing application takes a lot of time. You can support application by donating. There is no company behind this application and it takes away my free time. Every donation matters and does not matter how small it is!