-
Received:
<!-- 2019-11-12T15:07:01Z <<<< --> <message from='memberbot@xmpp.org/o8YlKiMR' xmlns='jabber:client' id='3a493e70-5348-48b3-90a6-e1faa4627d64-14E0' xml:lang='en' to='wojtek@tigase.org/792061310-tigase-54'> <composing xmlns='http://jabber.org/protocol/chatstates'/> </message> <!-- 2019-11-12T15:07:01Z <<<< --> <message from='memberbot@xmpp.org/o8YlKiMR' xmlns='jabber:client' id='3a493e70-5348-48b3-90a6-e1faa4627d64-14E1' type='chat' to='wojtek@tigase.org/792061310-tigase-54' xml:lang='en'> <body>Hi, wojtek@tigase.org!</body> </message> <!-- 2019-11-12T15:07:01Z <<<< --> <message from='memberbot@xmpp.org/o8YlKiMR' xmlns='jabber:client' id='3a493e70-5348-48b3-90a6-e1faa4627d64-14E3' type='chat' to='wojtek@tigase.org/792061310-tigase-54' xml:lang='en'> <body>Voting has begun for: Board, Council</body> </message> <!-- 2019-11-12T15:07:01Z <<<< --> <message from='memberbot@xmpp.org/o8YlKiMR' xmlns='jabber:client' id='3a493e70-5348-48b3-90a6-e1faa4627d64-14E6' type='chat' to='wojtek@tigase.org/792061310-tigase-54' xml:lang='en'> <body>By proceeding, you affirm that you wish to have your vote count as a proxy vote in the official meeting to be held on 2019-11-21T19:00Z in xsf@muc.xmpp.org.</body> </message> <!-- 2019-11-12T15:07:01Z <<<< --> <message from='memberbot@xmpp.org/o8YlKiMR' xmlns='jabber:client' id='3a493e70-5348-48b3-90a6-e1faa4627d64-14E9' type='chat' to='wojtek@tigase.org/792061310-tigase-54' xml:lang='en'> <body>You have already participated in this election. Would you like to recast your votes? (yes/no)</body> </message>
Message received when I have chat opened are displayed as in
beagle-first.png
and after reopening as inbeagle-second.png
-
I still experience the problem in
Version 3.4 (65)
Type |
Improvement
|
Priority |
Normal
|
Assignee | |
Spent time |
0
|
Issue Votes (0)
Watchers (0)
For some reason memberbot messages are displayed out-of-order when received with chat window open. Navigating to different chat and coming back to memberbot window shuffles them to correct order.
(It maybe somewhat related to #issue #163)