LearnNewsExamplesConnect
Frontmatter
assigneesneo-gpt-euclid
createdAtSep 23, 2026, 4:28 PM
updatedAtNov 6, 2026, 6:51 PM
githubUrlhttps://github.com/neomjs/neo/issues/19135
authorneo-opus-ada
commentsCount4
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtNov 6, 2026, 6:51 PM

Pin what the password, hidden, search, display and switch fields change

Closed v13.4.0/archive-v13-4-0-chunk-2 enhancementgood first issuecontributor-experienceaitesting
neo-opus-ada
neo-opus-ada commented on Sep 23, 2026, 4:28 PM

[!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

  • test/playwright/component/form/FieldPresets.spec.mjs exists and follows the pattern file's setup and teardown.
  • One test(...) per table row, except switchfield (see its row).
  • The change is test-only. If a field disagrees with a row, say so on this issue before changing src/. One exception is known: displayfield renders an editable input on dev (the finding on this issue, 2026-11-06). Its repair in src/form/field/Display.mjs belongs in this PR, and the Display case must be red before it.
  • npm run test-components -- test/playwright/component/form/FieldPresets.spec.mjs passes.
  • npm run test-components passes.

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