ddcb9cd02e
Phase 5 - BYOB Backend (TASK-007A/B): - LocalSQL Adapter with full CloudStore API compatibility - QueryBuilder translates Parse-style queries to SQL - SchemaManager with PostgreSQL/Supabase export - LocalBackendServer with REST endpoints - BackendManager with IPC handlers for Electron - In-memory fallback when better-sqlite3 unavailable Phase 3 - GitHub Panel (GIT-004): - Issues tab with list/detail views - Pull Requests tab with list/detail views - GitHub API client with OAuth support - Repository info hook integration Phase 3 - Editor UX Bugfixes (TASK-013): - Legacy runtime detection banners - Read-only enforcement for legacy projects - Code editor modal close improvements - Property panel stuck state fix - Blockly node deletion and UI polish Phase 11 - Cloud Functions Planning: - Architecture documentation for workflow automation - Execution history storage schema design - Canvas overlay concept for debugging Docs: Updated LEARNINGS.md and COMMON-ISSUES.md
TASK-013: Phase 3/4 Integration Bug Fixes
Status: 🔴 RESEARCH PHASE
Priority: P0 - Critical UX Issues
Created: January 13, 2026
Last Updated: January 13, 2026
Overview
Critical UX bugs introduced during Phase 2 (Task 8 - ComponentsPanel changes) and Phase 3 (Task 12 - Blockly Integration) that significantly impact core editing workflows.
These bugs affect basic node selection, property panel interactions, Blockly editor stability, and comment system usability.
Bugs
🐛 BUG-1: Property Panel "Stuck" on Previous Node
Priority: P0 - Blocks basic workflow
Status: Research needed
When clicking different nodes, property panel shows previous node's properties until you click blank canvas.
🐛 BUG-2: Blockly Node Randomly Deleted on Tab Close
Priority: P0 - Data loss risk
Status: Research needed
Sometimes when closing Blockly editor tab, the node vanishes from canvas.
🎨 BUG-2.1: Blockly UI Polish
Priority: P2 - UX improvement
Status: Ready to implement
Simple UI improvements to Blockly property panel (remove redundant label, add code viewer button).
💬 BUG-3: Comment System UX Overhaul
Priority: P1 - Significant UX annoyance
Status: Design phase
Comment button too easy to click accidentally, inconsistent positioning. Move to property panel.
🏷️ BUG-4: Double-Click Label Opens Comment Modal
Priority: P1 - Breaks expected behavior
Status: Research needed
Double-clicking node name in property panel opens comment modal instead of inline rename.
🪟 BUG-5: Code Editor Modal Won't Close on Outside Click
Priority: P1 - Significant UX issue
Status: Research needed
New JavaScriptEditor modal stays on screen when clicking outside. Should auto-save and close.
Implementation Phases
Phase A: Research & Investigation (Current)
- Investigate Bug 1: Property panel state synchronization
- Investigate Bug 2: Blockly node deletion race condition
- Investigate Bug 3: Comment UX design and implementation path
- Investigate Bug 4: Label interaction event flow
- Investigate Bug 5: Code editor modal close behavior
Phase B: Quick Wins
- Fix Bug 5: Code editor modal close (likely event propagation)
- Fix Bug 2.1: Blockly UI polish (straightforward)
- Fix Bug 4: Label double-click (likely related to Bug 1)
Phase C: Core Fixes
- Fix Bug 1: Property panel selection sync
- Fix Bug 3: Implement new comment UX
Phase D: Complex Debugging
- Fix Bug 2: Blockly node deletion
Phase E: Testing & Documentation
- Comprehensive testing of all fixes
- Update LEARNINGS.md with discoveries
- Close out task
Success Criteria
- Can click different nodes without canvas clear workaround
- Blockly tabs close without ever deleting nodes
- Blockly UI is polished and intuitive
- Comment system feels intentional, no accidental triggers
- Comment preview on hover is useful
- Double-click label renames inline, not opening comment modal
- Code editor modal closes on outside click with auto-save
- All existing functionality still works
- No regressions introduced
Files Modified (Expected)
Bug 1 & 4:
packages/noodl-editor/src/editor/src/views/nodegrapheditor.tspackages/noodl-editor/src/editor/src/models/sidebar/sidebarmodel.ts- Property panel files
Bug 2:
packages/noodl-editor/src/editor/src/views/CanvasTabs/CanvasTabs.tsxpackages/noodl-editor/src/editor/src/contexts/CanvasTabsContext.tsx
Bug 2.1:
packages/noodl-editor/src/editor/src/views/panels/propertyeditor/DataTypes/LogicBuilderWorkspaceType.ts
Bug 3:
packages/noodl-editor/src/editor/src/views/nodegrapheditor/NodeGraphEditorNode.ts- Property panel header components
- New hover preview component
Bug 5:
packages/noodl-core-ui/src/components/code-editor/JavaScriptEditor.tsxpackages/noodl-editor/src/editor/src/views/panels/propertyeditor/CodeEditor/CodeEditorType.ts
Related Tasks
- Phase 2 Task 8: ComponentsPanel Menu & Sheets (introduced Bug 1, 4)
- Phase 3 Task 12: Blockly Integration (introduced Bug 2, 2.1)
- LEARNINGS.md: Will document all discoveries
Notes
- All bugs are separate and should be researched independently
- Bug 2 is intermittent - need to reproduce consistently first
- Bug 3 requires UX design before implementation
- Bug 1 and 4 likely share root cause in property panel event handling
- Bug 5 is a quick fix - should be resolved early
Last Updated: January 13, 2026