Why was IndexedDB chosen for storing drafts and scenario states instead of localStorage or sessionStorage?

IndexedDB was chosen for storing drafts and script states because it offers more powerful capabilities compared to localStorage and sessionStorage:

• Storage capacity: IndexedDB allows storing significantly more data (hundreds of megabytes or more), whereas localStorage is limited to about 5-10 MB.
• Asynchronous operation: IndexedDB works asynchronously, not blocking the main thread, which improves performance and interface responsiveness.
• Structured data: IndexedDB supports storing complex structured objects, including indexes for fast searching.
• Persistent storage: Unlike sessionStorage, data in IndexedDB persists across browser sessions.

Thus, for storing large volumes of draft data and script states, which can be complex and require quick access, IndexedDB is the optimal choice.