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

Fix padding on search history row when performing a search with too many characters #1046

Closed
stavares843 opened this issue May 28, 2020 · 0 comments · Fixed by #1056
Closed
Labels
[Type] Bug Something isn't working.
Milestone

Comments

@stavares843
Copy link

  • When a user performs a search with just a few characters example 5 going again to the search, the search history displays the correct padding. When user performs a search with a long keyword such as 50 characters, the padding on the first row on search history is not displayed properly.

STR - Steps to reproduce

  • Compile develop branch
  • Go to Simple Note app
  • Login
  • Go to All Notes
  • Tap on search
  • Perform a search with just a few characters - (screenshot left side attached)
  • Exit search
  • Tap on search
  • Perform a search with a long keyword example 50 characters - (screenshot right side attached)
  • Exit search
  • Go to search again
  • The padding on the right side screenshot is not displayed properly

Expected

  • Padding on the right side screenshot should be the same displayed on the left side screenshot

Screenshot

Screenshot 2020-05-28 at 23 48 20

Make Model Android Version App Version
Google Pixel 2 G011A API 28, Android 9 2.6-rc-1 debug (Build 103) develop branch
@stavares843 stavares843 added the [Type] Bug Something isn't working. label May 28, 2020
@theck13 theck13 self-assigned this Jun 3, 2020
@theck13 theck13 added this to the 2.8 milestone Jun 3, 2020
@theck13 theck13 removed their assignment Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug Something isn't working.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants