[BUG] <form-builder> move icon is missing
@PrathameshHegde is already working on this.
Since Aug 10, 2026.
Assessment
This issue has not been assessed yet.
Description
Environment
- Hosting type
- Form.io
- Local deployment
- Version: 10.0.1
- Formio.js version: 5.3.1
- Frontend framework: Angular 20.3.0
- Browser: Chrome
- Browser version:
Steps to Reproduce
- Create a fresh Angular 20 project
- Install Form.io related dependencies
- Install FontAwesome 4 dependency (and update angular.json)
- Use
<form-builder>component
Expected behavior
When hovering an element, all icons should be shown
Observed behavior
Move icon is missing
Notes
The icon is not rendered because is referenced using fa-move class, which doesn't exist on "font-awesome": "^4.7.0". The correct class is fa-arrows (I manually changed the rendered HTML just to show you that it works)
- Dominant language
- TypeScript
- Stars
- 706
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from formio/angular
-
question
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
[BUG] "Left (Right-aligned)" label position causes misaligned error messages and descriptionsMay be free again @Victoriya25 claimed this 365 days ago, and no pull request is open. Openbug
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day