MerginMaps / MerginMaps/mobile

Multiline field with long text causes inconsistent form layout

Open
#4,604 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug forms ui/ux
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

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

  1. Open a project tester-ws-1 / tc05_forms_widgets_ containing a layer with a Multiline
  2. Create a new feature and enter a large amount of text or many rows in the multiline field.
  3. Save the feature.
  4. Tap on the saved feature to open the preview form
  5. 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.