[CP Staging] Fix: Android edge-to-edge related inset/padding issues#53223
[CP Staging] Fix: Android edge-to-edge related inset/padding issues#53223mountiny merged 33 commits intoExpensify:mainfrom
Conversation
|
🚧 @mountiny has triggered a test build. You can view the workflow run here. |
This comment has been minimized.
This comment has been minimized.
@c3024 please try again, i didn't yet push all commits sorry |
|
Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers! |
|
🚧 @mountiny has triggered a test build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
|
|
@chrispader Lint failures. |
just fixed |
Not reproducible on Pixel 7 Pro (Android 15) Let me try Xiaomi Redmi Note 5 Pro (Android 9) |
mountiny
left a comment
There was a problem hiding this comment.
The remaining issues feel like a minor user interface programs on android since we are not creating new android release for a production I think it's okay to move this fix to staging and then focus on the general fix for these safe area issues
Users are not blocked from taking the actions hence I don't think it should block the deploy
|
@allroundexperts basically approved with just one pending comment so I will go ahead with this merge. Chris and Kiryl cannot reproduce |
|
@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
|
ESLint failing because of the useOnyx migration which we wont do in this CP PR |
[CP Staging] Fix: Android edge-to-edge related inset/padding issues (cherry picked from commit 6430cd7) (CP triggered by mountiny)
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.0.67-8 🚀
@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes. |
|
🚀 Deployed to production by https://github.com/mountiny in version: 9.0.67-9 🚀
|
| <Button | ||
| onPress={() => toggleOption(item)} | ||
| style={[styles.pl2]} | ||
| style={[styles.pl2, insets.bottom ? styles.mb5 : undefined]} |
There was a problem hiding this comment.
This change has introduced a regression in #53261 , there is no need to add the extra margin.
| pressOnEnter | ||
| large | ||
| style={[styles.w100, styles.mb4, styles.ph4, styles.flexShrink0]} | ||
| style={[styles.w100, styles.mb5, styles.ph4, styles.flexShrink0]} |
There was a problem hiding this comment.
While handling missing styles, we missed noticing the size mismatch for Next button with the Manual tab. We fixed this in #60386





@mountiny
Explanation of Change
Fixes issues related to the recent merge of #52392. This PR adds missing styles for respecting the safe area (on Android). Where necessary, extra padding/margin styles were added. This PR also includes some minor code improvements and re-structuring in styles/StyleUtils.
Fixed Issues
$ #53161
$ #53205
$ #53190
$ #53215
PROPOSAL:
Tests
New chat/room screens
Submit/track expense (IOU)
Video attachments
Sidebar
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop