Skip to content

[$500] Workspace - The invite message can't fit into the textbox #37406

Closed

Description

@izarutskaya

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


Found when validating PR : #29991

Version Number: 1.4.44.0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal Team

Action Performed:

  1. Log in with a Gmail account
  2. Create a new workspace
  3. Tap on the "Invite members" button
  4. Select any suggested member
  5. Tap on the Invite button

Expected Result:

The invite message should fit into the textbox.

Actual Result:

The invite message can't fit into the textbox.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6395091_1709098760283!capture

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01561b4140b01dff6c
  • Upwork Job ID: 1763716186253737984
  • Last Price Increase: 2024-03-02

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 28, 2024
  2. melvin-bot commented on Feb 28, 2024

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. izarutskaya commented on Feb 28, 2024

    @izarutskaya
    Author

    @mallenexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  4. izarutskaya commented on Feb 28, 2024

    @izarutskaya
    Author

    We think that this bug might be related to #wave8-collect-admins
    CC @zanyrenney

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Mar 2, 2024
  6. changed the title [-]Workspace - The invite message can't fit into the textbox[/-] [+][$500] Workspace - The invite message can't fit into the textbox[/+] on Mar 2, 2024
  7. melvin-bot commented on Mar 2, 2024

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 2, 2024
  9. melvin-bot commented on Mar 2, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @paultsimura (External)

  10. mallenexpensify commented on Mar 2, 2024

    @mallenexpensify
    Contributor

    Think it can be external. @paultsimura , let me know if you disagree.
    Checking with Wave 6, collect submitter for project
    https://expensify.slack.com/archives/C02MW39LT9N/p1709337922878799

  11. 11 remaining items

  12. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    Also, I wasn't able to reproduce on iOS Safari

    Just duplicate your invite message to make it 2x as long

  13. dukenv0307 commented on Mar 4, 2024

    @dukenv0307
    Contributor

    The issue is that the welcome message is taller than the defined max height, and the message can be of any height, so there's no sense to just increase the max height to some other fixed value.

    @paultsimura I think the problem here is that the "default invite message" is clipped when it's shown to the user, it's supposed to always be showing in full when the user opens that page (if not the user will have to scroll to read the full text). The current max height was set based on that assumption too.

    Just duplicate your invite message to make it 2x as long

    If the user edits the invite message and it becomes longer than the text box, it's not a problem because at the time the user already reads the full text of the "default invite message"

  14. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    I think making it scrollable is a better alternative as in all the other platforms we are just making the invite message as scrollable

    From what I see – we have this message scrollable on all platforms. Could you please share the recordings on what platforms the message is not scrollable?

  15. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    If the user edits the invite message and it becomes longer than the text box, it's not a problem because at the time the user already reads the full text of the "default invite message"

    If I modify the message, leave the page, and go back to it – the new custom message will be "default" for all future invitations. So this is not necessarily related to the default invitation message set by Expensify.

    Screen.Recording.2024-03-04.at.12.50.31.mov
  16. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    Yes yes I know that and that's what I am saying that we should make the mweb Chrome : Android and mweb Safari : IOS scrollable for invite message textbox

    @godofoutcasts94 please try to keep the communication productive. From what I see, all the platforms (including both mWeb) already have this field scrollable. If you have a different experience - please provide the screen recording.

  17. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    @shawnborton just so you don't have to scroll through all the messages.

    TD;DR:
    The issue is that the welcome message is taller than the defined max height, and the message can be of any height, so there's no sense to just increase the max height to some other fixed value.

    However, the field is scrollable. Do we want to change this behavior? And if yes – what would be the expected outcome?

    Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-03-02.at.12.43.51.mp4

    #37406 (comment)
    #37406 (comment)

  18. dannymcclain commented on Mar 4, 2024

    @dannymcclain
    Contributor

    I'm down to wait for the other designers to chime in, but I think this is expected behavior and isn't something we need to do anything about. Looks to be working like a normal textarea input, which I think is a good and fine thing.

    One possible discussion point, if we end up having too much text and the user needs to scroll, when the user first sees the message, do we want to show them the top of the text or the bottom, assuming they're able to scroll down.

    @mallenexpensify I think it kinda depends on whether the field is focused or not. If the field is focused, we should continue to default to the end/bottom, because that's where we place your cursor in the input (I assume). If the field is not focused, then I could see an argument for defaulting to the top of the message, but honestly think either is fine.

  19. shawnborton commented on Mar 4, 2024

    @shawnborton
    Contributor

    Yeah I agree with Danny here - this seems to be standard textarea behavior.

    Did we recently change the max height or something?

  20. paultsimura commented on Mar 4, 2024

    @paultsimura
    Contributor

    Did we recently change the max height or something?

    Nope. I think the issue reporter just had a relatively small screen and a relatively long workspace name, so the default message overflowed the pre-defined textarea height.

    So would you suggest to close this issue? @shawnborton @dannymcclain

  21. shawnborton commented on Mar 4, 2024

    @shawnborton
    Contributor

    I would be good with that, yes.

  22. mallenexpensify commented on Mar 4, 2024

    @mallenexpensify
    Contributor

    Thanks all, closing

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2DesignExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions