Although I can't find it now but I'm sure I've seen a discussion previously - would it be worth adding some code to remove a socket.io connection error popping up in the console (for some browsers that honour the workaround).

For example, in Firefox when navigating to a new page I see this:

The connection to ws://www.example.dev:8888/socket.io/1/websocket/ry6Em-mIVVe96pRyDgH_ was interrupted while the page was loading.

Perhaps this can be hidden by socket disconnection prior to page unloading (maybe ignored by Chrome still?) but I'm not really sure how everything's meant to work.

				    $(window).on('beforeunload', function(){
					 Drupal.Nodejs.socket.disconnect();
				    });

It appears that without this code the page keeps trying to reconnect?

Comments

cmonnow’s picture

Issue summary: View changes
SocialNicheGuru’s picture