Bugzilla

We just paired on this, and made an attempt to simply take the `ChatWidget` code and get it running on a local html file, without `near-membrane` conflicting - in the hopes that we could set up the app to reproduce.  During pairing we couldn't get the settings of the `ChatWidget` class sufficiently loaded to cause the widget to do much. 

However, after the call I took a look again at the websites code, to see if it constructed the ChatWidget, and it does, with a large settings object. I was able to copy-paste the settings object and get it barely functioning (see attached) - we can see with this reduction that the `scw-active` class _is_ being applied on the `<div class="scw-btn scw-btn-send">` element! (To reproduce, simply load the html file and type in the textarea with the placeholder "countryPlaceholderUserInput".

So in other words it looks like perhaps the svelte component works fine in isolation, but either something with `near-membrane` (or perhaps the socket connection?) are causing sufficient issues to prevent this class applying. I would hazard a guess it might be `near-membrane` as I'm fairly sure that code proxies all application code through iframes.

We just paired on this, and made an attempt to simply take the `ChatWidget` code and get it running on a local html file, without `near-membrane` conflicting - in the hopes that we could set up the app to reproduce.  During pairing we couldn't get the settings of the `ChatWidget` class sufficiently loaded to cause the widget to do much. 

However, after the call I took a look again at the websites code, to see if it constructed the ChatWidget, and it does, with a large settings object. I was able to copy-paste the settings object and get it barely functioning (see attached) - we can see with this reduction that the `scw-active` class _is_ being applied on the `<div class="scw-btn scw-btn-send">` element! (To reproduce, simply load the html file and type in the textarea with the placeholder "countryPlaceholderUserInput", observing the pink square which appears).

So in other words it looks like perhaps the svelte component works fine in isolation, but either something with `near-membrane` (or perhaps the socket connection?) are causing sufficient issues to prevent this class applying. I would hazard a guess it might be `near-membrane` as I'm fairly sure that code proxies all application code through iframes.