Cmd+Shift+Enter comment submissions trigger 'Duplication comment detected'

[garrett-eclipse]

Hello,

Ran into this recently where submitting a comment using Cmd+Shift+Enter on Mac Chrome will trigger the 'Duplicate comment detected; it looks as though you’ve already said that!' message, going back I see the comment is actually created. This happens when logged in or out. And using the identical content but clicking submit instead of using the keyboard doesn't cause the issue.

Cheers

[garrett-eclipse]

Please excuse those first two screens I grabbed the wrong ones on upload, uploading the right ones and the above can be removed.

[garrett-eclipse]

Logged out submission

[garrett-eclipse]

Logged in submission

[afercia]

Please excuse those first two screens I grabbed the wrong ones on upload, uploading the right ones and the above can be removed.

I went ahead and removed them.

[garrett-eclipse]

Thanks @afercia, I appreciate that.

[afercia]

Seems to me the actual behavior is different depending on whether you’re logged in.

Non logged in: pressing only Enter submits the content.

Logged in: pressing Enter doesn't do anything. Pressing Cmd + Enter (macOS Chrome) triggers the error message.

@garrett-eclipse can you reproduce this (when you have a chance)? Also, not sure why you're pressing also Shift. Maybe I'm missing something :)

[garrett-eclipse]

Hi @afercia I can no longer seem to reproduce this using 5.3 so I am flagging for close.

I can only now seem to cause the message when it's actually duplicate content which is then the expected result.

If you can't reproduce any longer as well then let's close this out.

I believe I was trying Shift+Cmd+Enter because Cmd+Enter didn't seem to work. Both don't cause any issues now. As to your note on non-logged-in behaviour I believe you were in the name/email when you hit enter as they're required after the content. If you fill them and go back into the content Cmd+Enter is required to submit as it's a Textarea.

I appreciate you looking at this.

[afercia]

Thanks @garrett-eclipse. I can't reproduce either. Looks like the last changes in [45790] and [46700] fixed the issue.

To clarify: it was happening on trunk, correct?

[garrett-eclipse]

Thanks @afercia, I appreciate you finding the changesets. It definitely looks like those addressed the issue.

To confirm; yes it was happening for me on trunk but is no longer an issue on trunk or in 5.3.