GravityKit
Entry Lock Remains Active After Tab Closed; "Request Control" Returns No Response
When a user edits an entry and closes the tab after submitting changes, the entry remains locked for an extended period. Other users attempting to access the same entry receive a lock notification. Using the "Request Control" feature results in a "No Response" message with no subsequent unlock notification. This behavior leads to confusion and prevents timely collaboration.
Steps to Reproduce
- User A opens an entry and makes edits.
- User A submits the update and closes the tab.
- User B opens the same entry shortly afterward.
- User B sees a notification that the entry is locked by User A.
- User B clicks "Request Control".
- "No Response" is shown, and no unlock occurs.
Expected Behavior
After User A closes the tab, the lock should release in a timely manner or immediately if the session is terminated.
If "Request Control" is used and there is no active editing session, the entry should be unlocked and the requesting user notified.
Actual Behavior
The entry remains locked for several minutes after the tab is closed. "Request Control" shows "No Response" with no indication of when or whether the lock will be released.
