Language‑selector change isolates per‑language drafts in LeetCode editors

LeetCode automatically saves typed code as a draft tied to a specific problem and selected language. When a user changes the language dropdown, the editor displays the starter template or the last saved draft for that language, but the effect on previously saved drafts for other languages is unclear.

The precise goal is to determine whether switching the language selector replaces the current language‑specific draft with the new language's starter code, or whether both language drafts coexist and remain retrievable after subsequent resets or page reloads.

Key constraints include the lack of a formal public specification for draft persistence, the independent storage of each language's draft, and the possibility that a reset discards the current draft and restores the official starter template for the selected language.

Questions: 1. Does changing the language dropdown discard the draft for the previous language? 2. Are drafts for each language stored independently and retrievable after a language switch and subsequent reset? 3. How does logging in from another device affect the availability of language‑specific drafts?