The edits in the entity browser and media edits can feel sluggish. Currently a PATCH occurs when someone leaves the text field after modifying. If they quickly proceed to another it is now grayed out to prevent multiple in-flight PATCHES from the same UI session.
To remove the sluggish feeling, it would be worth exploring debouncing the PATCH if the user is "still editing". Once the user stops editing, the patch should occur. A visual indication of data that is not yet comitted to the database would be useful.
The edits in the entity browser and media edits can feel sluggish. Currently a PATCH occurs when someone leaves the text field after modifying. If they quickly proceed to another it is now grayed out to prevent multiple in-flight PATCHES from the same UI session.
To remove the sluggish feeling, it would be worth exploring debouncing the PATCH if the user is "still editing". Once the user stops editing, the patch should occur. A visual indication of data that is not yet comitted to the database would be useful.