[!NOTE]
Open for anyone. The #18985 first-timer reservation ended on 2026-10-31. Claim this issue with a comment.
The witness lives in the component tier: it tests something a person looks at, and #18985's tier rule sends those to a real browser.
Welcome 👋
Five of Neo's form fields are presets: a base field with a few configs changed. A password field is a text field whose input has type="password", and a display field is a read-only text field. Each is a handful of lines, and none has a test. One spec can pin all five by mounting each in a real browser, and you will see how Neo builds a field along the way.
This is a good first issue. It needs Node.js and a clone of this repository: no Docker, no AI setup.
Set up once: follow Set up the engine from a clone. The component tier starts its own server and builds the themes it needs on its first run.
Where things live
- Sources:
src/form/field/Password.mjs, Hidden.mjs, Search.mjs, Display.mjs and Switch.mjs.
- New test file:
test/playwright/component/form/FieldPresets.spec.mjs
- Pattern to copy:
test/playwright/component/component/Image.spec.mjs. It mounts a component into the empty test viewport with Neo.worker.App.createNeoInstance, reads the real DOM, and destroys it afterwards. Use the field's module (e.g. importPath: '../form/field/Password.mjs') and its ntype (passwordfield, hiddenfield, searchfield, displayfield, switchfield).
What to cover
| Field |
Expected in the DOM |
passwordfield |
its <input> has type="password" |
hiddenfield |
the field is not visible (Playwright's toBeHidden()) |
searchfield |
the field carries neo-searchfield and neo-textfield, shows no label, and its input's placeholder is Search |
displayfield |
its input is readonly with tabindex="-1", and no clear trigger renders |
switchfield |
the field carries neo-switchfield and neo-checkboxfield, and its input carries neo-switchfield-input. Already pinned by test/playwright/component/form/field/Switch.spec.mjs (2026-11-06), so no new case. |
Done when
Out of scope
The base Text and CheckBox fields, validation, and styling.
While you wait for review
You just pinned one small piece of a multi-threaded application engine. In Neo.mjs your app's code runs inside a web worker, and the main thread only paints. Two things are worth ten minutes:
- See the part nobody expects. Run
npm run build-themes -- -n -e dev -t all and npm run server-start, open apps/workstation/, and drag a tab out of the browser window. It becomes its own OS window, still running, with the same component instances and the same worker. Benefits: Introduction explains why that is possible.
- Your coding agent can go much further here. The skills this repository's AI maintainers work with are published on npm as
neo-agent-skills, and they need no Knowledge Base and no Memory Core. With Claude or GPT beside you, the help wanted issues are within reach after this one.
Maintainer notes
Curated under #18985 (Hacktoberfest 2026). Found work: no unit or component spec names these five modules on dev (2026-09-23).
Live latest-open sweep: the latest 20 open issues at 2026-09-23T14:24Z, with no equivalent (title searches return closed history only). A2A: no claim on this scope. Memory Core: no prior decision.
Revised 2026-11-06, after @neo-gpt-emmy's readiness note:
- the reservation is released, since it ended 2026-10-31;
- the paths, pattern and commands now match the stated component-tier decision;
- each row asserts what renders (input type, visibility, classes, placeholder,
readonly/tabindex), not the config values that produce it.
Origin Session ID: 3be453e4-8b04-4865-be62-4cff34f4e0c6
Welcome 👋
Five of Neo's form fields are presets: a base field with a few configs changed. A password field is a text field whose input has
type="password", and a display field is a read-only text field. Each is a handful of lines, and none has a test. One spec can pin all five by mounting each in a real browser, and you will see how Neo builds a field along the way.This is a good first issue. It needs Node.js and a clone of this repository: no Docker, no AI setup.
Set up once: follow Set up the engine from a clone. The component tier starts its own server and builds the themes it needs on its first run.
Where things live
src/form/field/Password.mjs,Hidden.mjs,Search.mjs,Display.mjsandSwitch.mjs.test/playwright/component/form/FieldPresets.spec.mjstest/playwright/component/component/Image.spec.mjs. It mounts a component into the empty test viewport withNeo.worker.App.createNeoInstance, reads the real DOM, and destroys it afterwards. Use the field's module (e.g.importPath: '../form/field/Password.mjs') and its ntype (passwordfield,hiddenfield,searchfield,displayfield,switchfield).What to cover
passwordfield<input>hastype="password"hiddenfieldtoBeHidden())searchfieldneo-searchfieldandneo-textfield, shows no label, and its input's placeholder isSearchdisplayfieldreadonlywithtabindex="-1", and no clear trigger rendersswitchfieldneo-switchfieldandneo-checkboxfield, and its input carriesneo-switchfield-input. Already pinned bytest/playwright/component/form/field/Switch.spec.mjs(2026-11-06), so no new case.Done when
test/playwright/component/form/FieldPresets.spec.mjsexists and follows the pattern file's setup and teardown.test(...)per table row, exceptswitchfield(see its row).src/. One exception is known:displayfieldrenders an editable input ondev(the finding on this issue, 2026-11-06). Its repair insrc/form/field/Display.mjsbelongs in this PR, and the Display case must be red before it.npm run test-components -- test/playwright/component/form/FieldPresets.spec.mjspasses.npm run test-componentspasses.Out of scope
The base
TextandCheckBoxfields, validation, and styling.While you wait for review
You just pinned one small piece of a multi-threaded application engine. In Neo.mjs your app's code runs inside a web worker, and the main thread only paints. Two things are worth ten minutes:
npm run build-themes -- -n -e dev -t allandnpm run server-start, openapps/workstation/, and drag a tab out of the browser window. It becomes its own OS window, still running, with the same component instances and the same worker. Benefits: Introduction explains why that is possible.neo-agent-skills, and they need no Knowledge Base and no Memory Core. With Claude or GPT beside you, thehelp wantedissues are within reach after this one.Maintainer notes
Curated under #18985 (Hacktoberfest 2026). Found work: no unit or component spec names these five modules on
dev(2026-09-23).Live latest-open sweep: the latest 20 open issues at 2026-09-23T14:24Z, with no equivalent (title searches return closed history only). A2A: no claim on this scope. Memory Core: no prior decision.
Revised 2026-11-06, after @neo-gpt-emmy's readiness note:
readonly/tabindex), not the config values that produce it.Origin Session ID: 3be453e4-8b04-4865-be62-4cff34f4e0c6