PolicyEngine / PolicyEngine/policyengine-app-v2
Mobile regressions in report output and parameter setter interfaces
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 50m
- Merged PRs (30d)
- 39
Description
Problem
Several calculator interfaces are still broken or difficult to use at mobile and narrow viewport widths.
Affected areas observed:
- Report output interface
- Parameter setter / policy parameter editing interface
Symptoms
- Interfaces appear horizontally compressed or shrunk.
- Content does not adapt well to narrow widths.
- Some controls or panels become difficult or impossible to interact with on mobile.
- Intermediate tablet-like widths should also be checked, not only the smallest mobile breakpoint.
Timing
This should likely be handled after the ui-kit integration and app/ directory cleanup, so we do not spend time patching layouts that are about to be replaced or reorganized.
Acceptance criteria
- Report output pages are usable at common mobile widths.
- Parameter setter / policy parameter editor is usable at common mobile widths.
- Critical controls are not clipped, compressed beyond usability, or hidden without an accessible alternative.
- Layout behavior is verified at iPhone SE width and intermediate tablet-ish widths.
- Desktop behavior remains unchanged.
Suggested investigation
- Audit report output layout components for fixed widths, min-widths, grid/table behavior, and overflow handling.
- Audit parameter setter views for full-screen/mobile layout assumptions.
- Verify which paths use StandardLayout, portals/full-screen shells, or custom modal/sheet layouts.
- Add focused responsive regression tests where feasible.
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.
Research direction
After the ui-kit integration and app/ directory cleanup, start by auditing the report output layout components and parameter setter views. Check StandardLayout, portals/full-screen shells, and custom modal or sheet layouts for fixed widths, min-widths, grids, tables, and overflow. Done means both areas work at iPhone SE and intermediate tablet widths without changing desktop behavior, with focused responsive regression tests where feasible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100