ryux1 opened a new pull request, #532:
URL: https://github.com/apache/fineract-backoffice-ui/pull/532

   ## What and why
   
   At phone widths, the client-creation stepper rendered every non-wrapping 
label in one row, while the surrounding Ionic card clipped the overflow. This 
keeps all numbered markers in view, gives layout space only to the active label 
below 600px, and exposes each translated label plus the current step to 
assistive technology. Wider layouts keep the existing presentation.
   
   Closes #489
   
   ## Verification
   
   - `WATCHPACK_POLLING=true CHOKIDAR_USEPOLLING=true npm run test:e2e -- 
e2e/mobile-shell.spec.ts --project=mobile --grep 'keeps every client-creation 
step reachable'` — passed against the mocked backend with the Pixel 7 profile
   - `npm test -- --watch=false` — 1,461 tests passed across 239 files
   - `npm run lint`
   - `npm run format:check`
   - `npm run check:icons`
   - `npm run i18n:check`
   - `npm run build`
   
   ## Screenshots
   
   The before state is captured in #489. The focused mobile browser test 
verifies the fixed geometry by asserting that the stepper does not overflow and 
all three markers remain within the viewport.
   
   ## Checklist
   
   - [x] I did not hand-edit generated files under `src/app/api/`.
   - [x] New component or service code uses the adapter boundary in 
`src/app/core/adapters/` instead of direct browser globals or imperative 
third-party APIs.
   - [x] User-facing strings use translation keys.
   - [x] I added or updated tests appropriate to this change, or explained why 
tests were not needed.
   - [x] UI workflow changes include suitable e2e coverage, including 
real-backend testing where relevant.
   - [x] Commits are signed — see [Commit 
Signing](CONTRIBUTING.md#commit-signing) in CONTRIBUTING.md.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to