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	241
title	Field picker z-index incorrect - seems to be CSS class names being munged
state	Closed
labels	bugstale
assignees	[]
createdAt	Feb 23, 2020, 8:01 PM
updatedAt	Oct 9, 2026, 10:02 PM
githubUrl	https://github.com/neomjs/neo/issues/241
author	keckeroo
commentsCount	4
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	1
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 28, 2024, 4:32 AM

Field picker z-index incorrect - seems to be CSS class names being munged

Closed v7.9.1/archive-v7-9-1-chunk-1 bugstale

keckeroo commented on Feb 23, 2020, 8:01 PM

Describe the bug The field picker appears under other items on the screen

To Reproduce Steps to reproduce the behavior:

Go to fields examples
Click on field picker
Picker appears under other items on screen which overlap picker area

Expected behavior Picker should always be top of z-index

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS] MacOSX
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22]

Additional context

keckeroo added the bug label on Feb 23, 2020, 8:01 PM

tobiu Feb 24, 2020, 11:37 AM

Hi Kevin,

thx for the report. There is indeed something wrong inside the picker field (adding more triggers messes with the CSS class-names).

Will take a look into it, by the latest when finishing the chip-field (which is needed for the RW2 app).

Best regards, Tobi

@github-actions - 2024-09-14T02:28:06Z

This issue is stale because it has been open for 90 days with no activity.

2024-09-14T02:28:07Z @github-actions added the stale label

@github-actions - 2024-09-28T02:32:25Z

This issue was closed because it has been inactive for 14 days since being marked as stale.

2026-09-16T10:26:48Z @neo-opus-ada cross-referenced by #18772

@neo-opus-grace - 2026-10-09T20:02:19Z

#19489 set C · T1 · Grace · 2026-10-09: confirm-close (obsolete). Thank you @keckeroo for the report. The picker was rebuilt as a floating container on document.body (src/form/field/Picker.mjs), so the 2020 CSS cause is gone.

2026-10-09T20:02:45Z @neo-opus-grace cross-referenced by #19489