-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$500] Android – Request – “Next step” is partly visible in the WS with IOU if device font size is larger #33950
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01cae7b1feabc7d940 |
Triggered auto assignment to @johncschuster ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.When we increase device font size, the Next Step text is partially visible because it's really big. What is the root cause of that problem?In the Next Step font size dynamically increases as we increase the system font size. We actually use a
Lines 375 to 379 in d5f5856
Line 49 in d5f5856
But we use RN Text component to render the Next Step, not our custom Text. Our custom text disable the system font scaling and handle it manually. What changes do you think we should make in order to solve the problem?Replace RN Text with our custom Text component. However, it still can't find the width of the badge. We can either create a static font size specifically for the Next Step or set a bigger max width and/or max height or dynamic width and height for the Next Step badge (using getValueUsingPixelRatio). |
@johncschuster, @c3024 Eep! 4 days overdue now. Issues have feelings too... |
@c3024 can you review the proposal above? Is it sufficient, or should we keep an eye out for more? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Have issues with building Android app. Will review ASAP. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@johncschuster @c3024 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@johncschuster, @c3024 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@c3024 how's your android build coming along? Are you still having trouble with it? |
@bernhardoj 's proposal here looks good to me. 🎀 👀 🎀 C+ Reviewed |
Triggered auto assignment to @hayata-suenaga, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Is this still reproducible? Seems fixed in #34325 |
Yes, it's fixed. I've not pulled the latest main when I reviewed it. Thanks. The issue can be closed. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.21-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
“Next step” is fully visible in the WS with IOU if device font size larger than the default .
Actual Result:
“Next step” is partly visible in the WS with IOU if device font size larger than the default .
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6332086_1704370958458.Next_steps.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: