Files
paseo/packages/app/e2e/mobile/diff-tree/README.md
Mohamed Boudra cb90806045 fix(app): soften the mobile diff tree button and remove row shadows (#4898)
Use a neutral surface for diff navigation and restrict Android elevation to document headers so shared tree rows stay flat after scrolling.
2026-09-15 17:06:21 +02:00

33 lines
1.6 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Mobile diff tree appearance
## Reproduce the row shadow
Use an Android emulator with a workspace containing 80 modified text files,
named `file-000.txt` through `file-079.txt`. Each file changes `before` to `after`.
1. Open the workspace's Changes sidebar, then **Jump to file**.
2. Swipe upward through the tree until `file-079.txt` is visible.
3. Inspect the row where the scroll gesture started. It must remain flat.
4. Swipe back to the first file, then return to the last file and select it.
The sheet should close and show that file's diff.
## Recorded verification
Android API 35, 1080×1920. The baseline produced a raised gray shadow around
`file-074.txt` after scrolling. The fixed build reached the same last row without
the shadow. Baseline scrolling in both directions and selection of the last file
passed; the fixed build also reached the last row and closed the sheet on selection.
The fixed-build assertion for the selected diff header did not match, so it does
not establish the final jump position.
| Before | After |
| ---------------------------------- | -------------------------------- |
| ![Row shadow](evidence/before.png) | ![Flat rows](evidence/after.png) |
| Light | Dark |
| --------------------------------- | ------------------------------- |
| ![Light diff](evidence/light.png) | ![Dark diff](evidence/dark.png) |
The shadow check is visual; the existing header-interaction unit test does not
test Android rendering. iOS, browser web, and Electron were not manually exercised.