Skip to content

[$250] Incorrect Button Size on "Invite Whisper" Modal #61905

Closed

Description

@m-natarajan

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: 9.1.44-6
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: @dubielzyk-expensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Navigate to any workspace
  2. @mention a user who's not on that workspace
  3. See the message with small buttons

Expected Result:

Buttons should be size "medium"

Actual Result:

Buttons are currently size "small"

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Image

Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021923391355281009698
  • Upwork Job ID: 1923391355281009698
  • Last Price Increase: 2025-05-16
Issue OwnerCurrent Issue Owner: @twisterdotcom

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 13, 2025
  2. melvin-bot commented on May 13, 2025

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. m-natarajan commented on May 13, 2025

    @m-natarajan
    Author

    Proposal by @dukenv0307

    Proposal

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

    The buttons on the "invite whisper" are size small

    What is the root cause of that problem?

    We forgot to add isMediumSized as true in actionableMentionWhisperOptions action like we did with others

    return [
    {
    text: 'actionableMentionWhisperOptions.invite',
    key: `${action.reportActionID}-actionableMentionWhisper-${CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.INVITE}`,
    onPress: () => resolveActionableMentionWhisper(reportID, action, CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.INVITE),
    isPrimary: true,
    },
    {
    text: 'actionableMentionWhisperOptions.nothing',
    key: `${action.reportActionID}-actionableMentionWhisper-${CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.NOTHING}`,
    onPress: () => resolveActionableMentionWhisper(reportID, action, CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.NOTHING),
    },
    ];
    }, [

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

    We should add isMediumSized as true

            {
                    text: 'actionableMentionWhisperOptions.invite',
                    ...
                    isMediumSized: true,
                    isPrimary: true,
            },
            {
                    text: 'actionableMentionWhisperOptions.nothing',
                    ...
                    isMediumSized: true,
            },
    

    return [
    {
    text: 'actionableMentionWhisperOptions.invite',
    key: `${action.reportActionID}-actionableMentionWhisper-${CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.INVITE}`,
    onPress: () => resolveActionableMentionWhisper(reportID, action, CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.INVITE),
    isPrimary: true,
    },
    {
    text: 'actionableMentionWhisperOptions.nothing',
    key: `${action.reportActionID}-actionableMentionWhisper-${CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.NOTHING}`,
    onPress: () => resolveActionableMentionWhisper(reportID, action, CONST.REPORT.ACTIONABLE_MENTION_WHISPER_RESOLUTION.NOTHING),
    },
    ];
    }, [

    Note: We should also check other actionable buttons to see if they are the correct size.

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    None UI bug

    What alternative solutions did you explore? (Optional)

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 16, 2025
  5. changed the title [-]Incorrect Button Size on "Invite Whisper" Modal[/-] [+][$250] Incorrect Button Size on "Invite Whisper" Modal[/+] on May 16, 2025
  6. melvin-bot commented on May 16, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 16, 2025
  8. melvin-bot commented on May 16, 2025

    @melvin-bot

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

  9. samoousama commented on May 16, 2025

    @samoousama

    Inside InviteToWhisperModal.js, or where the modal is rendered:

    <ConfirmModal
    ...
    confirmText "Invite"
    onConfirm={handleInvite}
    confirmButtonStyles={[styles.buttonLarge, styles.p5, styles.mt5]}
    confirmTextStyle={[styles.textStrong, styles.textNormal]}
    ...
    />
    If not using ConfirmModal, and the button is direct:
    <Button
    text="Invite"
    onPress={handleInvite}
    style={[styles.buttonLarge, styles.mt5]}
    textStyles={[styles.textStrong, styles.textNormal]}
    success
    />

    This aligns the button size with the design standards used across the app.

  10. melvin-bot commented on May 16, 2025

    @melvin-bot

    📣 @samoousama! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  11. 1 remaining item

  12. twisterdotcom commented on May 20, 2025

    @twisterdotcom
    Contributor

    How is this going @akinwale? Any good proposals yet?

  13. akinwale commented on May 21, 2025

    @akinwale
    Contributor

    @dukenv0307's proposal works here.

    @dukenv0307 could you post a comment on this issue so that you can be assigned?

    🎀👀🎀 C+ reviewed.

  14. melvin-bot commented on May 21, 2025

    @melvin-bot

    Triggered auto assignment to @pecanoro, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  15. pecanoro commented on May 21, 2025

    @pecanoro
    Contributor

    Assigning @dukenv0307 to the issue

  16. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 21, 2025
  17. dukenv0307 commented on May 22, 2025

    @dukenv0307
    Contributor

    This issue was fixed in: #62085. So I think we don't need to open the PR cc @akinwale

  18. akinwale commented on May 22, 2025

    @akinwale
    Contributor

    This issue was fixed in: #62085. So I think we don't need to open the PR cc @akinwale

    In that case, I believe this can be closed with 50% compensation due.

    cc @twisterdotcom

  19. twisterdotcom commented on May 23, 2025

    @twisterdotcom
    Contributor

    Payment Summary:

    • @akinwale paid $125 via New Expensify (Reviewer)
    • @dukenv0307 paid $125 via New Expensify (Contributor)
  20. JmillsExpensify commented on Jun 9, 2025

    @JmillsExpensify
    Contributor

    $125 approved for @dukenv0307

  21. JmillsExpensify commented on Jun 9, 2025

    @JmillsExpensify
    Contributor

    $125 approved for @akinwale

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 contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions