I've made a branch containing UI work for showing user avatars to master.
If you update the webcomponent then you should be getting the new changes. When in doubt, remove node_modules/conversejs and then run npm install to make sure you get the latest version.
In the interest of moving forward I've removed the last TODO list item in this ticket, which was to show a fallback image if no avatar image is set. Looking at your Rocket.chat instance, all users have avatars, so can we assume that this will be the case going forward, at least for now?
What's still needed for this ticket is to fetch the user avatar from the server, I'm currently working on that and expect to be finished with that by the end of tomorrow.
By JC Brand on 2018-04-30T15:28:29 (imported from GitLab project)
Thank you for this update JC.
Too bad this took that long but it is good you took the time to do it properly, I prefer to have a realiable component than to play it cheap.
I fully agree with you regarding the default avatar thing.
Let's assume everyone has one for now and later on, for the alpha or beta version of the application we will get back to it.
Good luck with the rest of the roadmap
By Alexandre on 2018-04-30T18:08:52 (imported from GitLab project)
One unfortunate limitation that XMPP servers have, which I found out while working on this issue, is that they can only return a user's avatar in a channel if that user is currently in the channel.
EDIT: There might be a way to work around this, by making all channels non-anonymous (so that user JIDs are available) and then maintaining member lists for all channels, but I think that's out of scope for this ticket, seeing as it already took a lot of time, and I think you guys should first try things out and decide whether it would be worth spending more time on avatars or not.
By JC Brand on 2018-05-02T14:54:51 (imported from GitLab project)