Have you refreshed the page (in Chrome, press F12, go to the network tab, disable caching, press F5). If this does not work, would you mind emailing me (
[email protected]) the full code for this page? From what I see it should work, but maybe something specific is in your code.
Just a side note I've seen myself this weekend on F5 and refreshing.
While rewriting the reconnect engine, I've noticed something very weird with refreshing a page. Pressing F5 in Chrome has different behaviours depending on the version and if the console is open:
Chrome 53.xxx + console open (F12): The page was reloaded and it passed through the ABMSessionCreator in B4J (CORRECT)
Chrome 53.xxx + console closed: The page was reloaded and it passed through the ABMSessionCreator in B4J (CORRECT)
Chrome 54.xxx + console open (F12): The page was reloaded and it passed through the ABMSessionCreator in B4J (CORRECT)
Chrome 54.xxx + console closed: No idea if the page was reloaded and it did NOT pass through the ABMSessionCreator in B4J (WRONG)
This raises some concern as ABMaterial heavily relies on Refreshing a page in the browser working correctly. I hope I have some workaround for this problem in the the Reconnect engine in 2.01. I'm currently updating the feedback app and the demo app to this new reconnect system. (It demands some changes in WebSocket_Connected, Page_ParseEvent and the ABMSessionCreator class. Don't worry, not that big and I've tried to make it as simple as possible).