[BUG] [v1.1.0] AuxiliarySidebar: onVisibilityChange runs on mount, not only on visibility changes

[tubel-hi]

Project

ide

Description

createEffect subscribes to auxiliaryBar.visible() and calls props.onVisibilityChange?.(visible) every time the effect runs, including its first run when the component mounts. That notifies consumers of the initial visibility as if it were a user-driven change, even though nothing toggled yet.

Error Message

Debug Logs

System Information

OS: Ubuntu
Context: Bounty Challenge v1.1.0

Screenshots

9.webm

Steps to Reproduce

Mount AuxiliarySidebar with an onVisibilityChange handler (e.g. log or state update).
Do not change auxiliary bar visibility.
Observe whether the handler runs on first paint.

Expected Behavior

onVisibilityChange runs only when visibility changes after mount (or behavior is documented as including initial sync).

Actual Behavior

Handler runs immediately on mount with the current auxiliaryBar.visible() value.

Additional Context

No response

[alejandrojhve2001-create]

Hi,i had work on this

[hinzwilliam52-ship-it]

/attempt #39592

[willkhinz]

/attempt #39592

[willkhinz]

/attempt #39592

[echobt]

✅ Validated

Bug confirmed in src/components/workbench/AuxiliarySidebar.tsx. The createEffect at lines 522-525 subscribes to auxiliaryBar.visible() and calls props.onVisibilityChange?.(visible) on every effect run, including the initial mount. This causes the callback to fire with the initial visibility value (false) before any user interaction occurs, incorrectly notifying consumers as if a visibility change happened. The video evidence clearly shows the console logging 'onVisibilityChange: false' immediately upon IDE reload, confirming the bug behavior.