Multiline field with long text causes inconsistent form layout
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- mobile
Research direction
No source file or test is named. Start by reproducing the saved multiline-field case on Android or iOS and trace the form's reopen/render path, comparing it with the layout after tapping the field. Done means the saved form opens with the multiline field correctly sized and its full content visible without interaction.
Written by the indexing model from the issue text.
Description
Description
When a feature containing a multiline field with a large amount of text or many rows is saved, reopening the feature form is in an inconsistent form layout. The form does not render correctly on open. The user is required to tap on the form field to trigger it to expand and display correctly.
Project: tester-ws-1 / tc05_forms_widgets
Environment
[x] Staging [x] PROD
Application (+ app version, build, operating system)
- Device: Samsung Galaxy A53 5G, Android 15
- App version: 2026.3.0 - 833251
- Device: IPhone 15 / iOS 26
- App version: 2026.3.0 - 26.7.927411
Steps to reproduce
- Open a project tester-ws-1 / tc05_forms_widgets_ containing a layer with a Multiline
- Create a new feature and enter a large amount of text or many rows in the multiline field.
- Save the feature.
- Tap on the saved feature to open the preview form
- Observe the multiline field layout when the form opens.
Actual results
- The feature form opens with an inconsistent layout — the multiline field is not rendered correctly and appears collapsed or incorrectly sized.
- The user must tap on the multiline field to trigger it to display the content properly.
Expected results
The feature form should open with the multiline field fully rendered and correctly sized, displaying all saved content without requiring any additional tap or interaction from the user.
Screenshots or logs
https://github.com/user-attachments/assets/75664ffe-b147-469a-b656-d5ad83c27c90
Conclusion
Created by Claude and supervised by a human test analyst.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 23
Contributor 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 MerginMaps/mobile
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
-
enhancement sync
MerginMaps/mobile#4713 · 2 assignees ·
-
enhancement performance qgis
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MerginMaps/mobile#4701 ·
All issues in MerginMaps/mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·