Skip to content

[$500] Expense - The gap between buttons in Concierge whisper is too wide #35168

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!


Version Number: 1.4.31.1
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: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1706185611151319

Action Performed:

  1. User A sends a payment to User B. Then User B @mentions user A in that same IOU thread.

Expected Result:

The space between the two buttons should only be 8-12px

Actual Result:

The gap between buttons in Concierge whisper is too wide

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

Add any screenshot/video evidence

CleanShot 2024-01-25 at 07 23 56@2x

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~010f9c7527fb2a6675
  • Upwork Job ID: 1750566867979767808
  • Last Price Increase: 2024-01-25

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 25, 2024
  2. melvin-bot commented on Jan 25, 2024

    @melvin-bot
  3. changed the title [-]Expense - The gap between buttons in Concierge whisper is too wide[/-] [+][$500] Expense - The gap between buttons in Concierge whisper is too wide[/+] on Jan 25, 2024
  4. melvin-bot commented on Jan 25, 2024

    @melvin-bot

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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 25, 2024
  6. melvin-bot commented on Jan 25, 2024

    @melvin-bot

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

  7. kbecciv commented on Jan 25, 2024

    @kbecciv
    Author

    We think that this bug might be related to #vip-vsb
    CC @quinthar

  8. bernhardoj commented on Jan 25, 2024

    @bernhardoj
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    The gap between invite and do nothing button is too big.

    What is the root cause of that problem?

    The gap is set to 16 here.

    <View style={[styles.flexRow, styles.gap4]}>

    Instead of 8/12

    What changes do you think we should make in order to solve the problem?

    Updat the gap to gap2 or gap3

  9. BhuvaneshPatil commented on Jan 25, 2024

    @BhuvaneshPatil
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Spacing between buttons is wide

    What is the root cause of that problem?

    We are using gap4 here, that's value is 16

    <View style={[styles.flexRow, styles.gap4]}>
    {props.items?.map((item) => (
    <Button
    key={item.key}
    style={[styles.mt2]}
    onPress={item.onPress}
    text={translate(item.text)}
    small
    success={item.isPrimary}
    />
    ))}
    </View>

    What changes do you think we should make in order to solve the problem?

    use gap3 or gap2

    What alternative solutions did you explore? (Optional)

  10. shawnborton commented on Jan 25, 2024

    @shawnborton
    Contributor

    I think we should do 8px as the solution, just to make that clear. cc @Expensify/design in case you disagree.

  11. shawnborton commented on Jan 25, 2024

    @shawnborton
    Contributor

    Also, would we have any interest in doing this one internally? Paying out $500 just for a tiny change seems a bit extreme, no?

  12. ishpaul777 commented on Jan 25, 2024

    @ishpaul777
    Contributor

    I am PR author for actionable mention whispers handling regressions in a follow up PR #34560, happy to include this in the PR

  13. shawnborton commented on Jan 25, 2024

    @shawnborton
    Contributor

    That would be wonderful!

  14. situchan commented on Jan 29, 2024

    @situchan
    Contributor

    Not overdue. @ishpaul777 please link this issue in your PR

  15. zanyrenney commented on Jan 30, 2024

    @zanyrenney
    Contributor

    @ishpaul777 I think we can close this and manage the change in your PR right? I don't think we need to keep this separate as you'll tackle it in that PR.

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.DailyKSv2ExternalAdded 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