Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profile "Save" button opacity inconsistent and looks disabled sometimes #10230

Closed
Beamanator opened this issue Aug 3, 2022 · 2 comments
Closed
Assignees
Labels
Daily KSv2 Engineering Reviewing Has a PR in review

Comments

@Beamanator
Copy link
Contributor

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Action Performed:

Edited profile information, saved, then edited profile info again

Expected Result:

The Save button should be full opacity - not dimmed at all

Actual Result:

The Save button is slightly dimmed, between 0.5 and 1 which makes it looks disabled, even though it isn't

Workaround:

Product still usable, just very confusing potentially

Platform:

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number:
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: Expensify employees
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1659521766977129?thread_ts=1659474255.603659&cid=C01GTK53T8Q

View all open jobs on GitHub

@melvin-bot
Copy link

melvin-bot bot commented Aug 3, 2022

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@Beamanator
Copy link
Contributor Author

Determined not a deploy blocker since product can still be used normally

I have done more investigation in the linked deploy blocker here: #10215 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2 Engineering Reviewing Has a PR in review
Projects
None yet
Development

No branches or pull requests

1 participant