New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Safari 8 - Retry button doesn't show up on messages that fail to send when off-line after reconnecting #1405
Comments
Hi @DschingisKahn, appreciate the report, can you let us know which Mattermost version you're on and which version of Safari? There is a known issue on Safari 8 in v1.2-RC1, |
This repros, ticket filed, progress can be tracked here: https://mattermost.atlassian.net/browse/PLT-1154 |
Thanks @DschingisKahn, re-opening as what you're describing we weren't able to repro. Would you be interested in trying it out on the test server our latest release at https://gitlab.mattermost.com/community/ and see if the issue is still there? |
Will try and report back! |
Safari 8 is not supported by that version, it seems :-). |
Hi @DschingisKahn, sorry, I forgot that Safari 8 support had been removed. There were multiple issues with Safari 8 discovered close to the release of Mattermost v1.2, and given the technical cost of supporting it, and declining market share, we ended up giving up support. Just tested on Chrome/Win7 using throttle to toggle online/offline and the Retry button seems to be working. Just curious, could you help us understand more about why you're using Safari 8 and Safari 9? It was a back-and-forth decision on making Safari 9 the minimum requirement, |
Thanks. It seems to be limited to Safari indeed (colleague had the same issue). I did not update yet to El Capitan, so that is why I am stuck with Safari 8 - no other reason. Let's not waste more time on this then (this feels a bit like good old IE times :-)) |
Hi @DschingisKahn, I've been able to repro the issue on our nightly builds server in Chrome/Win7: Since it's not limited to Safari, I'm switch this ticket back to the original name. Sorry for the back and forth. I'm not yet able to get a consistent repro, but we know that it's not-browser specific. Thanks again for the report! This is something we need to fix. |
Hi @it33, Glad you could reproduce it, that's a start :). A few colleagues encountered it in the last days. It happens when our VPN connection drops at the same time a message is sent. Safari and Chrome indeed. |
Closing this issue, it will tracked in Jira |
Accepting pull request ticket here for adding the option to cancel sending a pending message: https://mattermost.atlassian.net/browse/PLT-1042 |
The situation:
There is no sign of the message in the database and it does not show up in another browser (which makes sense of course). Clearing the cache brought no luck though.
When inspecting the element, I see that the data-reactid attribute ends with
$undefinedpostKey
and one of the nested div's hasid="undefined_message"
,class="post-waiting"
and again a data-reactid attribute that contains$undefinedpostKey
and$undefined_message
.The console throws the following warning:
Warning: flattenChildren(...): Encountered two children with the same key, '.1:$undefinedpostKey'. Child keys must be unique; when two children share a key, only the first child will be used.
The text was updated successfully, but these errors were encountered: