Skip to content

Onboarding - "Invite your team" task description is not styled correctly #56308

Closed

Description

@IuliiaHerets

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.0.94-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a new account.
  3. Select Manage my team's expenses.
  4. Selecting any organization size and accounting software.
  5. Go to #admins
  6. Open task "Invite your team".
  7. Go back and open task "Create a workspace".

Expected Result:

"Invite your team" and "Create a workspace" task description will be styled correctly.

Actual Result:

"Invite your team" and "Create a workspace" task description are not styled correctly. Some sentences are completely bold and the bold mark down is shown.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6732948_1738660877776.20250204_104134.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 4, 2025
  2. melvin-bot commented on Feb 4, 2025

    @melvin-bot

    Triggered auto assignment to @anmurali (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. melvin-bot commented on Feb 4, 2025

    @melvin-bot

    Triggered auto assignment to @nkuoch (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Feb 4, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Feb 4, 2025

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. IuliiaHerets commented on Feb 4, 2025

    @IuliiaHerets
    Author

    Production behaviour

    bandicam.2025-02-04.11-31-56-320.mp4
  7. NJ-2020 commented on Feb 4, 2025

    @NJ-2020
  8. ishpaul777 commented on Feb 4, 2025

    @ishpaul777
    Contributor

    its coming from -> #55222, confirmed with revert #56313

  9. NJ-2020 commented on Feb 4, 2025

    @NJ-2020
    Contributor

    Oops, Sorry

  10. c3024 commented on Feb 4, 2025

    @c3024
    Contributor

    @Amoralchik

    Could you raise a PR?

    We should avoid escaping text only for the trackExpense task and not for other tasks.

    Here

                    task.type === 'trackExpense' ? false : true,
  11. Amoralchik commented on Feb 4, 2025

    @Amoralchik
    Contributor

    @c3024

    I disagree that this is related to my changes. But I agree it's been detected this issue after implementing them.

    The main problem is handling shouldEscapeText in unescapeText in expensify-common.

    As we can see, the description starts with the <strong> tag, which causes the strange "Invite your team*" and only closes this tag after "*Invite member" in list item 4.This happens due to incorrect text processing, and as I noticed during testing, it is related to the presence of ">" in the text.

    I also need to fix other issues, so anyway I can add this to avoid shouldEscapeText for this text.

  12. izarutskaya commented on Feb 5, 2025

    @izarutskaya

    Issue is not reproducible

    Recording.2839.mp4
    Recording.2975.mp4
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.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions