Skip to content

[HOLD for payment 2023-06-12] [$1000] Padding above “no result found” error in message input “Emoji- Search bar” is not consistent. #18909

@kavimuru

Description

@kavimuru

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 “Chats”
  2. Click “Emoji”.
  3. Search an invalid Emoji, so that “no result found” error appear.
  4. Observe that the bottom padding of the input field is 8px 16px.
  5. Please note that all below search bar reflects padding of 0px 20px 12px on search of an invalid item.
    Search bar next to chats.
    Send money- select a currency.
    Profile- Pronouns
    Profile- Timezone
    DOB-Year

Expected Result:

Padding for the error “No result found” should be consistent among pages.

Actual Result:

Padding for the error “No result found” is not consistent among pages.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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.13.2
Reproducible in staging?: y
Reproducible in production?: y
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
1 (1)
2 (1)
Untitled

Expensify/Expensify Issue URL:
Issue reported by: @usmantariq96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684009587168949

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01399c717b42532302
  • Upwork Job ID: 1658488402800201728
  • Last Price Increase: 2023-05-30

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
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