What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9531
title	Grid SortZone incorrectly intercepts column resize drag events, causing VDOM corruption and layout thrash
state	Closed
labels	bugaigrid
assignees	tobiu
createdAt	Mar 20, 2026, 10:46 PM
updatedAt	Mar 20, 2026, 10:48 PM
githubUrl	https://github.com/neomjs/neo/issues/9531
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 20, 2026, 10:48 PM

Grid SortZone incorrectly intercepts column resize drag events, causing VDOM corruption and layout thrash

Closed v12.1.0/archive-v12-1-0-chunk-2 bugaigrid

tobiu commented on Mar 20, 2026, 10:46 PM

Description

When resizing a grid column (using grid.header.plugin.Resizable), the draggable.grid.header.toolbar.SortZone was concurrently intercepting the same drag:start, drag:move, and drag:end events because both plugins listen to the same header button DOM nodes.

This caused the SortZone to execute its column-reordering logic during a resize operation. Specifically, SortZone.onDragStart would falsely identify a column as being dragged and set its columnPosition.hidden = true and cell.style.visibility = 'hidden'. This led to grid cells vanishing during resize. Furthermore, SortZone.onDragEnd would needlessly trigger grid.body.createViewData(false, true), causing massive performance degradation by forcing a full, un-recycled VDOM regeneration of the entire grid body on every resize.

Solution

Mutex via Config: Repurposed the dragResortable config on the header toolbar as a runtime semaphore.
Resizable Plugin: Modified grid.header.plugin.Resizable to set toolbar.dragResortable = false on drag:start and restore it to true on drag:end. Also optimized the toolbar lookup from owner.up() to owner.parent.
SortZone Bailouts: Added strict if (!me.owner.dragResortable) return; bailouts to the very top of onDragStart, onDragMove, and onDragEnd in draggable.grid.header.toolbar.SortZone. This cleanly severs the event processing if a resize is active.
Cleanup: Removed the now-obsolete delete cell.style.visibility; "self-healing" hack from grid.Body#updateCellPositions since the underlying VDOM corruption is prevented entirely.

tobiu Mar 20, 2026, 10:48 PM

Fixed in 2ed06e864