We are using the uddeIM API to use uddeim features in another component of our website and have had two user complaints about the same issue since upgrading to 2.3. The users cannot send a message in in our component using Firefox and Chrome (IE is OK - imagine that!) - the button doesn't respond at all. However, they can send using the main uddeim Compose screen. We cannot reproduce the issue here using the exact same browser/OS and JavaScript settings.
The only difference we can see is that in our component we are using the feature that disables the send button when it is clicked, and converts it to "processing", which we saw in the 2.2 version of uddeIM. But now we don't see that feature in the Compose screen of uddeIM (still in the API, though). Is there something about that we should know? Any other toubleshooting steps we can take?
I also notice that the multiple message problem is back on uddeIM since the Send button is no longer disabled after sending. Is this a setting? - can't find it.
1. The API does not provide any functionality to disable a button. When *you* provide a component with Javascript code that disables a button, you have to check this code.
2. Yes, it is correct that uddeIM 2.3 behaves like uddeIM 2.1 (the button will not longer disabled). The reason is that the button was still disabled when the user used the browser's back button and retyped a message he was not able to send the new message.
3. Double posting is a typical layer 8 problem: Depending on the server and network load it might take 1-2 secs to get a feedback that the message has been send. When a user clicked a button twice the message has been send twice.
