New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep conversationId and userID when opening chat in new tab #989

serpino opened this Issue May 25, 2018 · 2 comments


3 participants

serpino commented May 25, 2018

Bot Info

  • SDK Platform: .NET Core
  • SDK Version: Core
  • Active Channels: WebChat, DirectLine
  • Deployment Environment: Azure Bot Service, Azure App Service, Bot Emulator

Issue Description

I want to host the chat within our website. In this web there are links that open the web in another tab. When I open the chat in a new tab, I receive in the message type conversationUpdate, a different conversationID and userID, when in fact it is the same user following the same conversation.

Is there any way that if that chat opens in different tabs of the browser is considered the same conversation?

P.D: I'm integrating the chat with directLine so I can customize the css and js files if necessary.


This comment has been minimized.

serpino commented May 28, 2018

Can you help me please?



This comment has been minimized.


compulim commented Jun 14, 2018

Preservation and continuation of history is not quite working today. We are planning to make it a feature in coming milestone.

In the meanwhile, I think you need to manipulate the DirectLineJS object to achieve that. Instead of passing a botConnection into Web Chat, you pass a directLine object in.

I have some old code trying to explore the area, may be it is helpful for you.

  conversationId: this.state.conversationID,
  domain: 'http://localhost:3001/mock',
  secret: null,
  streamUrl: this.state.conversationID ? 'http://nostreamsupport' : null,
  token: this.state.conversationID ? 'null' : null,
  watermark: this.state.watermark,
  webSocket: false
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment