XMPP.send proposes me to connect (pop-up) when I connected with XMPP.open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SamePlace |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
In the API: XMPP, I want to use the XMPP.open instead of XMPP.up because I need to send a home-made presence (with negative priority being sent to the server and with a specific Resource Application Priority, XEP-0168, as well as Entity Capabilities, XEP-0115).
XMPP.open "works", but unfortunately it seems the rest of the library does not consider me to be connected. So when I execute XMPP.send to send my specific presence stanza with this account, it pops up a dialog window with a list of the available accounts (and the one I use is not even in this list. Anyway Sameplace is deactivated, I use only xmpp4moz).
So instead I must use "XMPP.up" and immediately after connection, I send a new presence stanza to override the previous one. It works well but this is not good because if ever I am not connected with another client elsewhere and that there are offline messages for instance, they will be sent to my extension just after XMPP.up (and before the new presence). Hence as my plugin is not done at all for chating, the offline messages will be lost, unprocessed.
This does not affect current HEAD (http:// github. com/bard/ sameplace and http:// github. com/bard/ xmpp4moz) where XMPP.up() no longer takes care of requesting roster and sending initial presence, and responsibility is delegated to client code instead.