Skip to content

Domains - Badge next to Domains tab is orange in light mode #102005

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.92-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #101227
Email or phone of affected tester (no customers): applausetester@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • App is in light mode.
  • As Expensifail domain member, go to Workspaces > Domains > applause.expensifail.com > Request admin access.
  • Log in as Expensifal domain admin and perform the steps below:
  1. Go to staging.new.expensify.com
  2. Go to Workspaces > Domains.
  3. Click applause.expensifail.com
  4. Go to Domains members.
  5. Open test tool via CMD+D > enable Simulate failing network requests.
  6. Deny the request.
  7. Click app back button.

Expected Result:

Badge next to Domains tab should be red in light mode.

Actual Result:

Badge next to Domains tab is orange in light mode and red in dark mode.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7266944_1790148225246.2.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7266944

Activity

  1. applause-bot commented on Sep 23, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/a86fc34c57a0840005a986649b332490d6531cf7e08a86cf597a5b1c32ef81a8

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 23, 2026
  3. melvin-bot commented on Sep 23, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #101227

  4. github-actions commented on Sep 23, 2026

    @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. melvin-bot commented on Sep 23, 2026

    @melvin-bot

    @mountiny @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #101227

  6. melvin-bot commented on Sep 23, 2026

    @melvin-bot

    @adamgrzybowski you have been assigned to this deploy blocker because you authored the offending PR: #101227

  7. melvin-bot commented on Sep 23, 2026

    @melvin-bot

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

  8. ZhenjaHorbach commented on Sep 23, 2026

    @ZhenjaHorbach
    Contributor

    But wait
    It should be orange in both cases?
    No?
    Cc: @shawnborton

  9. shawnborton commented on Sep 23, 2026

    @shawnborton
    Contributor

    No, it looks correct - it flips based on theme. Going to close.

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

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions