Skip to content

[$250] Chat - Text in compose box blends with background when theme was changed in device settings #39348

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!


Version Number: 1.4.58-4
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+omq23@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition: user should be Signed In and "Use Device Settings" option should be selected for theme option in Preferences

Web, Desktop and mWeb steps:

  1. Open https://staging.new.expensify.com/

  2. Open any chat

  3. Navigate to device settings and change the theme to the opposite color

  4. Navigate back to browser or app

  5. Write any text in compose box

iOS steps:

  1. Open https://staging.new.expensify.com/

  2. Open any chat

  3. Write any text in the compose box

  4. Navigate to device settings and change the theme to the opposite color

  5. Navigate back to app

Expected Result:

Text should be properly displayed in compose box.

Actual Result:

The text in the compose box retains its original color despite changes to the background color. Consequently, it blends with the background when the device theme is switched to the opposite color.

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

Bug6432761_1711819047019.Screen_Recording_2024-03-30_at_19.06.10.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01b5c49154255020bb
  • Upwork Job ID: 1776299979557351424
  • Last Price Increase: 2024-04-05

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Apr 1, 2024

    @melvin-bot

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

  4. github-actions commented on Apr 1, 2024

    @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.
  5. izarutskaya commented on Apr 1, 2024

    @izarutskaya
    Author

    @anmurali 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.

  6. izarutskaya commented on Apr 1, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #vip-vsb.

  7. izarutskaya commented on Apr 1, 2024

    @izarutskaya
    Author

    Production

    Bandicam.2024-04-01.13-52-24-147.mp4
  8. MariaHCD commented on Apr 1, 2024

    @MariaHCD
    Contributor

    Able to reproduce the issue when switching to dark mode on staging web Chrome:

    Screen.Recording.2024-04-01.at.4.30.53.PM.mov

    Wasn't able to repro on desktop, however.

  9. 64 remaining items

  10. tomekzaw commented on Apr 8, 2024

    @tomekzaw
    Contributor

    Should be fixed with #39872.

  11. melvin-bot commented on May 2, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @hoangzinh, @tomekzaw, @thienlnam, @BartoszGrajdek eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  12. BartoszGrajdek commented on May 13, 2024

    @BartoszGrajdek
    Contributor

    @thienlnam can we get this tested & closed?

  13. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    and removed
    ReviewingHas a PR in review
    on May 13, 2024
  14. mallenexpensify commented on May 21, 2024

    @mallenexpensify
    Contributor

    Added @anmurali back as BZ (not sure if they're needed though, we just need BZs added to all bugs, in case they are).

  15. mvtglobally commented on May 22, 2024

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  16. mallenexpensify commented on May 23, 2024

    @mallenexpensify
    Contributor

    Closing, also unable to repro (and.. now I'm in dark mode!)
    image

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.EngineeringMonthlyKSv2retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions