Feature Request / Bug Report: Content Fragment Lock Not Honored in New Editor - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	New Content Fragment Editor does not honor JCR locking
Use-case:	In the new Content Fragment editor, JCR locks applied to CF nodes (jcr:lockOwner, jcr:lockIsDeep) are ignored. This allows other users to open, edit, and save CFs even when another user has locked the CF — breaking workflow integrity and increasing risk of data loss.
Current/Experienced Behavior:	Lock applied on CF node via workflow or API is respected in the old editor (UI prevents edits). In the new editor, the same CF is still editable by all users. No lock icon or warning shown to other users.
Improved/Expected Behavior:	The new CF editor must respect JCR-level locks like the classic editor. CFs should: Display a lock indicator with username. Prevent edits and saves by users other than the lock owner. Show a warning like “This CF is locked by [user]”
Environment Details (AEM version/service pack, any other specifics if applicable):	Lock CF via workflow step or Node.lock() API. Open CF in classic editor → Editing is blocked (). Open same CF in new editor → Editing allowed ().
Customer-name/Organization name:	JNJ
Screenshot (if applicable):
Code package (if applicable):

[#2]

@TharunMi1 Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-34849. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.