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	8620
title	Implement Element.moveBefore() support for Atomic Moves
state	Closed
labels	aicore
assignees	tobiu
createdAt	Jan 13, 2026, 11:08 PM
updatedAt	Jan 13, 2026, 11:35 PM
githubUrl	https://github.com/neomjs/neo/issues/8620
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 11:35 PM

Implement Element.moveBefore() support for Atomic Moves

Closed v11.21.0/archive-v11-21-0-chunk-1 aicore

tobiu commented on Jan 13, 2026, 11:08 PM

The current atomic move implementation in Neo.main.DeltaUpdates.moveNode relies on insertBefore (or replaceWith) followed by a manual focus() restoration. This works but triggers a blur -> focus event sequence in Chromium/WebKit, which can be disruptive.

The new Element.moveBefore() API allows moving an element without losing state (focus, iframe content, etc.) natively.

Requirements:

In DeltaUpdates.moveNode, detect if parentNode.moveBefore is available.
If available, use parentNode.moveBefore(node, siblingRef) instead of insertBefore.
Skip the manual focus() restoration logic if moveBefore is used, as it preserves focus natively.
Retain the current fallback logic for browsers that do not support moveBefore (e.g., Safari).

References:

MDN: https://developer.mozilla.org/en-US/docs/Web/API/Element/moveBefore

tobiu Jan 13, 2026, 11:35 PM

Input from Gemini 3 Pro:

✦ I have implemented the requested changes:

Added nativeMoveBefore class field to Neo.main.DeltaUpdates for caching feature detection results.

Updated moveNode to check for moveBefore support on the first run.

If supported, moveNode now uses parentNode.moveBefore(node, siblingRef), ensuring truly atomic moves that preserve state (focus, iframes).

If not supported (e.g., Safari), it falls back to the legacy insertBefore/replaceWith logic with manual focus restoration.

Verified via npm test (249 tests passed). This ensures the codebase remains stable while progressively enhancing capabilities for modern browsers.

coderabbitai cross-referenced by PR #740 on Aug 17, 2026, 7:40 AM