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	8907
title	Regression: LoadMask no longer showing in Big Data Grid example
state	Closed
labels	bugairegression
assignees	tobiu
createdAt	Jan 30, 2026, 10:07 AM
updatedAt	Jan 30, 2026, 10:08 AM
githubUrl	https://github.com/neomjs/neo/issues/8907
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 30, 2026, 10:08 AM

Regression: LoadMask no longer showing in Big Data Grid example

Closed v11.24.0/archive-v11-24-0-chunk-1 bugairegression

tobiu commented on Jan 30, 2026, 10:07 AM

Description

The "Is Loading" mask in the Big Data Grid example (examples/grid/bigData) stopped appearing during heavy operations (e.g., changing "Amount Rows" or "Amount Columns").

Root Cause

Recent changes in src/mixin/VdomLifecycle.mjs introduced an await new Promise(resolve => setTimeout(resolve, 1)); inside executeVdomUpdate. This forces the VDOM update process to yield to the macrotask queue.

In examples/grid/bigData/ControlsContainer.mjs, the code sets isLoading = 'Is Loading' and immediately triggers a heavy synchronous operation (e.g., grid.store.amountRows = ...).

Because the App Worker is single-threaded, the synchronous data generation operation blocks the event loop. The setTimeout callback in executeVdomUpdate is starved until the heavy operation completes, causing the "Loading" mask update to be sent too late (after the work is already done).

Fix

Manually yield execution in ControlsContainer.mjs after setting the loading state but before triggering the heavy operation. This allows the VDOM update macrotask to run and flush the mask state to the DOM.

Impact

examples/grid/bigData/ControlsContainer.mjs

Proposed Changes

Add await me.timeout(5); in:

onAmountColumnsChange
onAmountRowsChange
onFilterFieldChange
onControlsToggleButtonClick (already present, ensuring consistency)

Verification: User has verified the fix locally.

tobiu Jan 30, 2026, 10:08 AM

Input from Gemini 3 Pro:

✦ I have applied the fix to examples/grid/bigData/ControlsContainer.mjs by introducing a me.timeout(5) yield. This ensures the VDOM update has time to dispatch the 'Loading' state before the App Worker is blocked by the heavy data generation process.

Changes committed in 0fe6cd300.