-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: missing copy icons and social icons on Android #20528
Conversation
…android(magic numberOfLines)
@NikkiWines @aimane-chnaif One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WorkspaceReimburseView
is also using CopyTextToClipboard
so update that as well.
src/pages/signin/Socials.js
Outdated
style={[styles.mr1, styles.mt1]} | ||
shouldUseAutoHitSlop={false} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this change for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mr1 is for spacing between icons. mt1 is for row spacing in cases icons are wrapped.
If shouldUseAutoHitSlop
is enabled, touch area of the pressable gets larger. To prevent this, we need to disable it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any difference between with shouldUseAutoHitSlop={false}
and without.
Can you explain more detail with screenshots?
Edit: nvm, I found issue on iOS. I see now why hitSlop should not be applied here
> | ||
{props.isDelayButtonStateComplete && props.textChecked ? props.textChecked : props.text} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you replace mr1 with space?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mr1 in this context doesn't work. That's why I replaced it with space
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok this regression came from another PR. But that's good to fix it here as it's simple.
Also I found another 2 regressions happening on production:
- copy icon is not center aligned vertically
- copy icon is not highlighted even though cursor changed to pointer changes to pointer
Screen.Recording.2023-06-13.at.11.48.27.AM.mov
This can be out of scope as it doesn't seem simple solution.
cc: @NikkiWines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I think it's fine to make those separate issues but please note it in the PR so that our QA team doesn't mark them as regressions from this PR. Once this is live, they should be reported as new bugs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR updated
@s-alves10 did you check this? Sorry I meant |
Fixed |
src/pages/signin/Socials.js
Outdated
style={[styles.mr1, styles.mt1]} | ||
shouldUseAutoHitSlop={false} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any difference between with shouldUseAutoHitSlop={false}
and without.
Can you explain more detail with screenshots?
Edit: nvm, I found issue on iOS. I see now why hitSlop should not be applied here
I've fixed all you mentioned. Will you check it again? |
Keyboard accessibility bugs:
I think this is not a blocker as we're not focusing accessibility issues for now. keyboard.accessibility.mov |
Reviewer Checklist
Screenshots/VideosWebweb.movMobile Web - Chromemchrome.movMobile Web - Safarimsafari.movDesktopdesktop.movios2.moviOSios1.movAndroidandroid.mov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NikkiWines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of small suggestions
{/* Workaround to fix https://github.com/Expensify/App/issues/17368. | ||
TODO: Remove `numberOfLines` once https://github.com/facebook/react-native/pull/35703 is merged and applied to our repo */} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove these comments, they clutter up the code and we don't know when that PR is going to be merged.
Instead, I think it's better to link to facebook/react-native#35703 in the PR Details
section and provide the same context there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@s-alves10 thanks for updating the code. What I meant above is that you should add details from that comment to the PR Details
section (see screenshot) so that anyone who comes back to this PR in the future knows the context of why this was modified like this and what PR we're waiting on.
> | ||
{props.isDelayButtonStateComplete && props.textChecked ? props.textChecked : props.text} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I think it's fine to make those separate issues but please note it in the PR so that our QA team doesn't mark them as regressions from this PR. Once this is live, they should be reported as new bugs.
PR details updated and comments were removed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@s-alves10 please see this comment about updating the PR description Applause team, please note the bugs identified by @aimane-chnaif here and here should be categorized as new bugs and not regressions from this PR 🙇 |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
❗ Please, do not use Github auto-linking keywords such as these: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved. For more details, see the Contributing Guidelines, specifically Submit your pull request for a final review 📖. |
1 similar comment
❗ Please, do not use Github auto-linking keywords such as these: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved. For more details, see the Contributing Guidelines, specifically Submit your pull request for a final review 📖. |
🚀 Deployed to staging by https://github.com/NikkiWines in version: 1.3.28-0 🚀
|
🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀
|
Details
Fixed Issues
$ #17368
PROPOSAL: #17368 (comment)
Note: This PR is a workaround to fix #17368. Current version of react-native has some bugs in
Text
component.numberOfLines
should be removed once facebook/react-native#35703 is merged and applied to our repoTests
Offline tests
QA Steps
Please note the bugs identified by @aimane-chnaif here and here should be categorized as new bugs and not regressions from this PR
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Web
17368_mac_safari.mp4
Mobile Web - Chrome
17368_android_chrome.mp4
Mobile Web - Safari
17368_ios_safari.mp4
Desktop
17368_mac_desktop.mp4
iOS
17368_ios_native.mp4
Android
17368_android_native.mp4