The discussion revolves around the skeleton loader in the chat drawer. Don reports that the loader is active even when messages are already loaded, contrary to the intended behavior of only showing it on initial load, as stated in a commit. Don provides examples of this issue, where the loader appears when clicking on replies or links to previous messages in the same channel. mcwumbly clarifies that the skeleton is a feature to improve the scrolling experience when messages are not yet loaded. joffreyjaffeux initially reports fixing the issue, but later finds that it’s still present on desktop, not just mobile. Eventually, joffreyjaffeux confirms that the issue has been fixed.
Hello,
I place this in Contribute > UX because it is works but seems it is only active in drawer and there was a commit to shows skeleton only on initial load. PERF: applies optimisations on chat-live pane - Pull Request #20532 - discourse/discourse - GitHub and it seems there is a problem with positioning too but it is maybe cause the loader.
Thanks 
I’m a bit unclear about what expectation you have here which is not being met.
Are you seeing the skeleton when you don’t expect to ? Or are you expecting to see the skeleton in some case but not seeing it?
On full page chat desktop or mobile this is not use skeleton because of performance.
can this skeleton load icon be made for normal pages as well?
Oh, OK. I think I understand.
The skeleton itself is a “feature”. We show it when messages are not yet loaded to improve the experience of scrolling.
I think what you’re pointing out here is that there is an unexplained and/or unexpected performance difference in loading earlier messages when in the drawer mode, and your evidence of that is that the skeleton appears.
Is that what your getting at?
I think skeleton should only be active on initial load when you open a channel. The commit I linked above contains this on description “show skeleton only on initial load” which works fine on full page chat desktop and mobile. Only drawer keeps skeleton for this purpose and this is why I think this is not by design.
Now it uses always when you click to show a reply or a link to a previous message in the same channel even if the message is loaded. Here is an example the replied message is already loaded.
Im pretty sure I fixed this the other day, I just tried and it didnt cause a full reload to click a reply.
EDIT: apparently it works on mobile, but not on desktop, weird. Will have a look.
This should have been fixed 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.