Skip to content

[$2000] mweb/safari - Request money - The header is disappearing for small screens #9061

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Access staging.new.expensify.com
  2. Log into any valid account
  3. Tap the green "+" icon and then "Request money"
  4. Input any money value and tap "Next"
  5. Tap on any user to proceed with the flow
  6. On the final comment page, tap on the text box "What's it for"

Expected Result:

The user expects the screen to adjust properly to the keyboard being opened

Actual Result:

The "Request X Amount" header disappears/ gets cut off by the phone margins when the keyboard is opened. The smaller the phone screen the bigger the issue is

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Mobile Web/safari

Version Number: 1.1.62.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5575485_Header_is_getting_cut_off_by_the_device_screen.mp4

Upwork job link: https://www.upwork.com/jobs/~0122be359424fe2943

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

Activity

  1. melvin-bot commented on May 17, 2022

    @melvin-bot

    Triggered auto assignment to @neil-marcellini (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  2. parasharrajat commented on May 18, 2022

    @parasharrajat
    Member

    This is how safari handles the input focus. The main problem here is the layout. safari Mobile does not respect flexbox when the keyboard is open. May be due to the momentum scroll. But I agree that we should find a fix for this problem once and for all.

    The correct fix would be able to fix the part of the UI position. For example, the bottom CTA, header. There is no direct solution available at the moment but this can be researched further to find hacks to the problem.

  3. added
    ImprovementItem broken or needs improvement.
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 18, 2022
  4. melvin-bot commented on May 18, 2022

    @melvin-bot

    Triggered auto assignment to @michaelhaxhiu (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  5. neil-marcellini commented on May 18, 2022

    @neil-marcellini
    Contributor

    Hmm actually hold on, I'm unable to reproduce this. Can someone else give it a try?

  6. removed their assignment
    on May 18, 2022
  7. michaelhaxhiu commented on May 26, 2022

    @michaelhaxhiu
    Contributor

    Just reproduced it myself:

  8. 97 remaining items

  9. parasharrajat commented on Aug 25, 2022

    @parasharrajat
    Member

    I can reproduce this on iPhone 13 mini.

  10. parasharrajat commented on Sep 6, 2022

    @parasharrajat
    Member

    No response on my last post. Waiting for new takers.

  11. mvtglobally commented on Sep 13, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (Second week) Not sure of this is device specific

  12. changed the title [-][$1000] mweb/safari - Request money - The header is disappearing for small screens[/-] [+][$2000] mweb/safari - Request money - The header is disappearing for small screens[/+] on Sep 15, 2022
  13. iwiznia commented on Sep 16, 2022

    @iwiznia
    Contributor

    So some people can still reproduce this, right? Should we double the price?

  14. parasharrajat commented on Sep 16, 2022

    @parasharrajat
    Member

    It is device-specific #9061 (comment). But Not sure if we need to increase its price. Because the solution will be hacky. Safari is all about hacks. We have one approach above which could do this trick but not sure how it will perform on all screens.

  15. mvtglobally commented on Sep 20, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (Third week)

  16. iwiznia commented on Sep 26, 2022

    @iwiznia
    Contributor

    ok, given solving this is too hacky, it is kind of how the browser works and the fact that nothing is really broken, let's close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.WeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions