Calling `panel.api.close()` and then calling `addPanel({ ... })` to restore the panel display does not work.

[gcokee]

Dockview version
5.2.0

Framework
Vue 3

Browser
electron 29.2.0

Describe the bug
Setting renderer: "always" in addPanel and then calling panel.api.close() followed by addPanel({ ... }) to add the closed panel results in an error. Setting renderer: "onlyWhenVisible" and then calling panel.api.close() followed by addPanel({ ... }) to add the closed panel again results in the tabComponent not being rendered.

Reproduction

If a sandbox isn't possible, provide steps to reproduce:

1. Go to '...'
2. Click on '...'
3. See error

Expected behavior
What you expected to happen.

Screenshots / recordings
If applicable, add screenshots or screen recordings.

Additional context
Any other relevant context (error messages, stack traces, related issues).

[mathuo]

Thanks for the report! I tried to reproduce this on master (current 6.5.0) and was unable to — both scenarios work for me:

• renderer: "always": addPanel → panel.api.close() → addPanel({ id: 'panel1', ... }) does not throw.
• renderer: "onlyWhenVisible" (default): same sequence — the tabComponent re-renders correctly on the re-added panel.

I tested at both the dockview-core layer (direct API) and the dockview-vue layer (real <DockviewVue> mount).

You're on 5.2.0 — a number of fixes in this area have landed since then (notably #1170 for dockview-vue framework-prop runtime updates, plus several render-overlay fixes). Could you try:

1. Upgrade to dockview-vue@6.5.0 and re-test.
2. If it still reproduces, please share:
   • The full error message and stack trace for the renderer: "always" case.
   • The exact addPanel(...) call signature you use the second time (same id? position/tabComponent/renderer?).
   • A minimal sandbox — forking one of the templates from https://dockview.dev would be quickest.

Without a sandbox or stack trace I can't pinpoint what's different in your setup vs. my repro. Happy to dig deeper as soon as you can share one of those.

[gcokee]

Thanks for the report! I tried to reproduce this on master (current 6.5.0) and was unable to — both scenarios work for me:

• renderer: "always": addPanel → panel.api.close() → addPanel({ id: 'panel1', ... }) does not throw.
• renderer: "onlyWhenVisible" (default): same sequence — the tabComponent re-renders correctly on the re-added panel.

I tested at both the dockview-core layer (direct API) and the dockview-vue layer (real <DockviewVue> mount).

You're on 5.2.0 — a number of fixes in this area have landed since then (notably #1170 for dockview-vue framework-prop runtime updates, plus several render-overlay fixes). Could you try:

1. Upgrade to dockview-vue@6.5.0 and re-test.

2. If it still reproduces, please share:

   • The full error message and stack trace for the renderer: "always" case.
   • The exact addPanel(...) call signature you use the second time (same id? position/tabComponent/renderer?).
   • A minimal sandbox — forking one of the templates from https://dockview.dev would be quickest.

Without a sandbox or stack trace I can't pinpoint what's different in your setup vs. my repro. Happy to dig deeper as soon as you can share one of those.

Thanks for the report! I tried to reproduce this on master (current 6.5.0) and was unable to — both scenarios work for me:

• renderer: "always": addPanel → panel.api.close() → addPanel({ id: 'panel1', ... }) does not throw.
• renderer: "onlyWhenVisible" (default): same sequence — the tabComponent re-renders correctly on the re-added panel.

I tested at both the dockview-core layer (direct API) and the dockview-vue layer (real <DockviewVue> mount).

You're on 5.2.0 — a number of fixes in this area have landed since then (notably #1170 for dockview-vue framework-prop runtime updates, plus several render-overlay fixes). Could you try:

1. Upgrade to dockview-vue@6.5.0 and re-test.

2. If it still reproduces, please share:

   • The full error message and stack trace for the renderer: "always" case.
   • The exact addPanel(...) call signature you use the second time (same id? position/tabComponent/renderer?).
   • A minimal sandbox — forking one of the templates from https://dockview.dev would be quickest.

Without a sandbox or stack trace I can't pinpoint what's different in your setup vs. my repro. Happy to dig deeper as soon as you can share one of those.

I tried upgrading to version 6.5.0, but the software layout became messed up. All the panels are crammed onto the far left of the software, arranged from top to bottom, and some modules are pushed to the bottom and out of view. I'd like to know if the internal layout or the parameters of the addPanel method changed after upgrading from 5.2.0 to 6.0.0 or later.