What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

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

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9482
title	Firefox Nightly: Scroll wheel stuck on Portal home page due to scroll-snap-type mandatory
state	Closed
labels	bugai
assignees	tobiu
createdAt	Mar 15, 2026, 8:20 PM
updatedAt	Mar 15, 2026, 9:39 PM
githubUrl	https://github.com/neomjs/neo/issues/9482
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 15, 2026, 9:07 PM

Firefox Nightly: Scroll wheel stuck on Portal home page due to scroll-snap-type mandatory

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v12.1.0 bugai

tobiu commented on Mar 15, 2026, 8:20 PM

Describe the bug On the portal app home route (apps/portal/view/home/MainContainer.mjs), we use a CSS-based "snappy" scrolling to enforce page-by-page scrolling (scroll-snap-type: y mandatory).

This works fine in Chrome and Safari. However, in Firefox Nightly (v150), using the mouse wheel makes it virtually impossible to scroll down. The scroll increments from the wheel are too small to break the mandatory threshold for the 100vh sections, causing Firefox to snap back to the current element.

To Reproduce

Open the portal app in Firefox Nightly.
Go to the home route.
Try to scroll down using the mouse wheel.

Expected behavior The user should be able to scroll to the next section using the mouse wheel.

Solution We will apply a CSS feature query targeting Firefox to downgrade the snapping behavior to proximity. This allows free scrolling with the mouse wheel while still snapping when close to a boundary.

@supports (-moz-appearance: none) {
    scroll-snap-type: y proximity;
}

tobiu added the bug label on Mar 15, 2026, 8:20 PM

tobiu added the ai label on Mar 15, 2026, 8:20 PM

tobiu cross-referenced by #7372 on Mar 15, 2026, 8:21 PM

tobiu assigned to @tobiu on Mar 15, 2026, 8:22 PM

tobiu referenced in commit 57a6558 - "style: Firefox Nightly scroll-snap fix for zero-width elements (#9482)" on Mar 15, 2026, 9:06 PM

tobiu Mar 15, 2026, 9:07 PM

Input from Gemini 3.1 Pro:

✦ We successfully identified and resolved the root cause of the scroll wheel lock in Firefox Nightly.

Diagnosis: The issue was not the JavaScript events, the OffscreenCanvas, or the general CSS scroll-snap-type rules. The culprit was the interaction between Firefox's layout engine, scroll-snap-type: mandatory, and a zero-width element using CSS scroll-driven animations (animation-timeline: --page-scroll).

The .portal-home-progress component, which is the first child in the DOM flow of the snapping container, used scale: 0 1; for its initial state. In Firefox, placing an element with an effective width of 0 at the very top of a scroll container while it evaluates a scroll intersection for a snap point triggers a calculation failure. It assumes the wheel delta is insufficient to break the 0 threshold, causing the viewport to snap immediately back to scrollTop: 0.

Resolution: The fix is surprisingly simple but highly specific. By changing the initial scale state from scale: 0 1; to scale: 0.001 1;, the element's bounding box is mathematically non-zero. This infinitesimally small value is completely invisible to the user but allows the Firefox layout engine to properly calculate the scroll intersections and release the snap lock when the user scrolls down from the Hero section.

A detailed comment has been added to the SCSS file to document this engine-specific hack for future reference.

tobiu closed this issue on Mar 15, 2026, 9:07 PM

tobiu Mar 15, 2026, 9:39 PM

opened a FF bugreport, to give the team a heads-up: https://bugzilla.mozilla.org/show_bug.cgi?id=2023455