Because of the isFrameMessage() issue in #722 , frame messages are initially displayed with a poorly animating message tail intended for text-only messages.
So I have opened a PR that's supposed to fix #722 so let's see if it fixes that one too. However until we detect a message is a frame (network request to parse headers) it will still be displayed as a text message?
Because of the isFrameMessage() issue in #722 , frame messages are initially displayed with a poorly animating message tail intended for text-only messages.