Webchat Documentation mixed

[Sahil_Gambhir]

Hey,

We have been getting a bunch of complaints about customers losing connection and not being reconnected. In my investigation I found that if I open up a chat and then put my computer into sleep mode for a little bit and then coming back causes the system to lose connection and then not regain connection when I come back. This also only happened on renderFrame calls; When renderPopup was used the system handled connection better.

I was looking at the documentation again because it has changed since I implemented it; One change is reflected on frame rendering. It changed from renderFrame({containerEl: 'chat-container'}) to {containerEl: document.getElementById('chat-container')} as seen below.

return webchat.renderFrame({
                 containerEl: document.getElementById('chat-container')
             }).catch(function(error) {
                 console.error('Error starting chat');
                 console.error(error);
             });

The documentation also says below that example: Note: In this example, containerEl refers to the id of the chat container div tag. This tag is shown in the example page below. But the example contains not just the ID but a getter to get the full tag.

The reason I am writing is. This change only shows up in this first example; all the other examples use, what I assume is, the old version. We are still testing but I think the returning the element seems to be working better and I was just making sure this is what was intended and if the documentation is still being updated.

Thanks

[anon19111426]

Hello,

How long did you wait between putting your computer to sleep and attempting to continue the Webchat? We have a reconnect timeout of 5 minutes for rejoining an in progress Webchat.

Both methods you describe for specifying the container are supported, but it does look like the documentation is inconsistent there. Thanks for pointing that one out, we'll review the documentation around it and make it clearer.