Skip to content

Dispose Rooster editor initialized after unmount - #536

Open
squarepots wants to merge 1 commit into
ProtonMail:mainfrom
squarepots:fix/rooster-editor-unmount-dispose
Open

squarepots wants to merge 1 commit into
ProtonMail:mainfrom
squarepots:fix/rooster-editor-unmount-dispose

Conversation

@squarepots

@squarepots squarepots commented Sep 7, 2026 •

Copy link
Copy Markdown

Move asynchronous Rooster editor ownership into the effect instance that starts initialization. Each instance tracks its own cleanup state, disposes stale initialization before onReady, and stores a live editor before onReady so synchronous unmount still disposes it.

Add focused lifecycle coverage for initialization completing after unmount, normal mounted cleanup, synchronous unmount from onReady, and stale initialization under React Strict Mode.

Verification

Fixes #535

@squarepots squarepots changed the title Fix Rooster editor disposal after async unmount Sep 7, 2026
@squarepots
squarepots force-pushed the fix/rooster-editor-unmount-dispose branch 2 times, most recently from 25890ba to 2b55f4e Compare September 7, 2026 10:12
@squarepots

squarepots commented Sep 18, 2026 •

Copy link
Copy Markdown
Author

Hi @nico3333fr, would you mind taking a look at this and the two related Rooster fixes, #538 and #540, when you have a chance? They’re all small, focused one-commit fixes with regression coverage. Thanks!

@mmso
mmso force-pushed the main branch 7 times, most recently from 57fccbd to c51e81b Compare October 1, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant