File locking blocks seamless switching from online to local editing

Recently with Text files (md and txt) I often have issues that they are "locked" by the Text app, or my server account.

If I quickly (or even not soo quickly) switch between editing them collaboratively online, and in my local text editor, the local version is locked and I get issues. Then need to close it online and wait for lock release
Also, the "lock" icon in the web interface is a bit misleading if added because someone on the web works on it, as in that case it is totally fine to collaborate (same actually for Office).

Before, I didn’t experience any issues, new things just synced down, the editor updated the file in the background, and the switch was seamless. And there was no confusion regarding a lock icon showing up even though everyone was just collaborating online.

@juliushaertl @AndyScherzinger @nimishavijay any thoughts on that? Also cc @karlitschek regarding the seamless local edinting & locking for Office.
Should we have some exceptions here, or could that create issues?

No files, tests, or entry points are named. Start by reproducing a quick switch between online editing and a local editor for an .md or .txt file, then trace when the lock is created and released. Done should define whether seamless switching can be restored safely and whether the web lock indicator accurately reflects collaboration.