Nextcloud Desktop Client doesn't detect conflicts

Dear friends,
I’ve just done a few tests and this is my findings testing a shared folder with files inside it and modifying them concurrently with another tester.

The shared folder has 2 files, a .docx and a .txt.

Scenario 1:

  1. I open the .docx and change something, but don’t save it just yet
  2. My colleague opens the .docx, modifies something else, and saves it pushing it to the server
  3. I save my version, and after a few seconds I get the conflict: locally I see my colleague’s version with the proper file name, and my copy saved as conflicting with the timestamp

This is the expected and desired behaviour.

Scenario 2:

  1. I open the .txt and change something, but don’t save it just yet
  2. My colleague opens the .txt, modifies something else, and saves it pushing it to the server
  3. I see in Windows’ file explorer that the .txt file gets dowloaded from the server
  4. I save my version, and I do not get any conflict warning, and even worse, my version actually does get pushed to the server, overriding my colleagues and making all his changes disappear and get lost

This is not the expected and desired behaviour, and it’s causing us to lose incremental updates to files, which for us is the whole point of having a tool like this.

Why is nextcloud not generating a conflict for non Microsoft Office files?

Thank you very much,
Roberto

Noone else has noticed this issue?