Closed badfiles closed 3 months ago
Can you provide some debug info? There's not enough info in your report for me to be able to help.
I tried to collect debug info, but it is pretty hard to accomplish. While I can see bosh packets, WebSocket packets are encrypted. Which debug info would you like to see?
Set debug
to true
when calling converse.initialize
and check if any errors or warnings are logged in the browser console. Also, use an unminified build of converse.js so that we get sane line numbers in any tracebacks.
The minified build does not work on my test browser, the discussion is somewhere in issues, same regex problem. I saw no errors when debug was on. If I looked at raw traffic with Wireshark, I saw the names in packets from the server. As I have mentioned earlier, I cannot determine what exactly causes the bug. I even saw the names once when the connection was via WebSocket. One thing is 100% reproducible -- if the names appeared, they are replaced with jid after clicking on them.
Here's what happens after loading the roster, the bosh connection leaves people 'unclicked'. the WebSocket connection somehow 'clicks' every item, it happens pretty fast, hard to notice. Anyway, after mysterious 'autoclick' or manual clicking an item, a name becomes a jid.
Ok, so initially you have nicknames, and then somehow they turn into JIDs. I guess what's happening is that nicknames are gotten from the roster, and then vcards are fetched and then nicknames are overwritten with JIDs because there isn't a fullname in the vcard.
building w/o "converse-vcard", // XEP-0054 VCard-temp
and/or setting use_vcards: false,
did not help.
Hmm, then I have no idea what's going on.
Refs #690
@badfiles do you still experience this issue?
Closing due to no response and AFAICT it's fixed.
Something strange happened to roster names. If I connect over websocket, I see no nicknames at all. If I connect over bosh, I see nicknames, but first click on a user leaves jid instead of a nickname.