Skip to content

[HOLD for payment 2023-06-21] [$1000] Inconsistency of the [Yes] button color between “Contact method” & “Security” modal #20130

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!


Action Performed:

  1. Open your profile.
  2. Click on " Contact methods".
  3. Click on " New contact method".
  4. Click on " Delete" to remove the existing contact.
  5. Notice the modal, “Yes” button is highlighted in red.
  6. Now go back and click on "Security".
  7. Click on " Close account".
  8. Enter default contact method
  9. Click on " Close account" button.
  10. Notice the modal, “Yes” button is highlighted in green.

Expected Result:

In both cases, the “Yes” button should be highlighted in red (and it should be this way across all UI elements in newDot).

Actual Result:

In this case, the “Yes” button is highlighted in different color (i.e. green vs red)

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.23.6

Reproducible in staging?: yes

Reproducible in production?: yes

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

Notes/Photos/Videos: Any additional supporting documentation

20230531_144448.mp4
Recording.2966.mp4

Expensify/Expensify Issue URL:

Issue reported by: @usmantariq96

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685527140262479

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01dad0214cbc98129a
  • Upwork Job ID: 1666465549069123584
  • Last Price Increase: 2023-06-07

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions