Localization Switching Bug

[nguyenvandang205]

Describe the Bug

When switching between locales, the Lexical editor fails to re-render properly. This results in the following issues:
• The editor content becomes unclickable and uneditable.
• The toolbar disappears or becomes unresponsive.
• The entire editor appears broken until the page is refreshed.

This behavior suggests the Lexical instance is not correctly reset or remounted on locale change.

Link to the code that reproduces this issue

pnpx create-payload-app@latest -t blank

Reproduction Steps

I don’t have a reproduction repo at the moment, but here are clear reproduction steps:

1. Go to the Admin panel.
2. Create or edit a document that uses the Lexical editor.
3. Switch to a different locale (e.g., from "en" to "vi").
4. After switching, the Lexical editor fails to re-render:
   • The content box becomes unclickable.
   • The toolbar disappears or is unresponsive.
   • You cannot type or edit the content anymore.

Expected behavior:
Lexical should re-render properly and remain editable after switching localization.

Environment:

• Payload version: [your version]
• Plugin: @payloadcms/richtext-lexical
• Browser: [e.g., Chrome 125]
• OS: [e.g., macOS Sonoma]

Please let me know if a minimal reproduction is required — I can provide one later if needed.

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

pnpm payload info

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload