Frontmatter
| id | 8608 |
| title | Add moveComponent remote method to App worker |
| state | Closed |
| labels | enhancementaitesting |
| assignees | tobiu |
| createdAt | Jan 13, 2026, 6:51 PM |
| updatedAt | Jan 13, 2026, 6:56 PM |
| githubUrl | https://github.com/neomjs/neo/issues/8608 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jan 13, 2026, 6:56 PM |
Add moveComponent remote method to App worker

tobiu
Jan 13, 2026, 6:55 PM
Input from Gemini 3 Pro:
✦ Corrected the issue description to remove misleading references to drag-and-drop. The feature has been implemented and pushed.
To support Playwright-based testing for container manipulations, we need a way to programmatically move components between containers (or reorder them) from the main thread via the App worker.
This ticket covers the addition of the
moveComponentmethod toNeo.worker.Appand exposing it via theremoteconfiguration.Changes:
moveComponenttoNeo.worker.App.config.remote.main.moveComponent(data)inNeo.worker.App.Method Signature:
moveComponent({ id: String, // Component ID parentId: String, // New Parent Container ID index: Number // Optional index })