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

Skin tone selector does not have the same dimensions as the emoji list #5247

Closed
isagoico opened this issue Sep 14, 2021 · 28 comments
Closed

Comments

@isagoico
Copy link

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:

  1. Navigate to a conversation
  2. Open emoji picker
  3. Click on the skin color selector

Expected Result:

Skin selector emojis should have the same dimensions and design as the rest of the emoji list.

Actual Result:

Skin selector emojis have a different height and don't have rounded edges as the rest of the emojis.

Workaround:

No need, visual issue.

Platform:

Where is this issue occurring?

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

Version Number: 1.0.98-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

image

image

Expensify/Expensify Issue URL:

Issue reported by: @parasharrajat
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1631558477208900

View all open jobs on GitHub

@MelvinBot
Copy link

Triggered auto assignment to @michelle-thompson (Design), see these Stack Overflow questions for more details.

@MelvinBot
Copy link

Triggered auto assignment to @TomatoToaster (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@parasharrajat
Copy link
Member

It should be marked as a deploy blocker as the new skin tone selector has issues.
The second part where some emojis have different dimensions is a side-effect and should be marked as regression.
Platform

  1. Web - (Firefox > 81)

@isagoico
Copy link
Author

This issue is already in production so I don't think it should be marked as deploy blocker. It was added here #4456

@parasharrajat
Copy link
Member

Thanks for pointing out the PR causing the Regression @isagoico. #4456. @mananjadhav Could you please take a look and confirm?

@mananjadhav
Copy link
Collaborator

Thanks for posting this. Yeah, it's a part of PR #4456. It didn't come across in the review and the testing that we'll need them to be of the same size.

I'll check and fix this.

@kadiealexander
Copy link
Contributor

Hi @mananjadhav, I've placed this issue on hold as per this update, as we are prioritising issues related to a feature release scheduled for 9/24. As an apology for the delay, we will add a $100 bonus as a thank you for waiting.

@parasharrajat
Copy link
Member

Its a regression @kadiealexander I don't think there will be a job for this.

@mananjadhav
Copy link
Collaborator

I am not sure if we would count it as regression. This PR was under review for over a month and this never came up. @stitesExpensify can comment on this

@kadiealexander
Copy link
Contributor

Will leave this for @stitesExpensify to decide :)

@mananjadhav
Copy link
Collaborator

Thanks. Just to add, I am not expecting a separate Job posting for this one :)

@stitesExpensify
Copy link
Contributor

I wouldn't consider it a regression because it never worked in the first place. I'd say this is more of an easy bug fix that should have a small job

@MelvinBot
Copy link

@mananjadhav Eep! 4 days overdue now. Issues have feelings too...

@mananjadhav
Copy link
Collaborator

PR under review

@MelvinBot MelvinBot removed the Overdue label Sep 22, 2021
@MelvinBot
Copy link

@mananjadhav Huh... This is 4 days overdue. Who can take care of this?

@MelvinBot
Copy link

@mananjadhav Still overdue 6 days?! Let's take care of this!

@mananjadhav
Copy link
Collaborator

PR under review and n6-hold

@MelvinBot MelvinBot removed the Overdue label Sep 29, 2021
@MelvinBot
Copy link

@mananjadhav Huh... This is 4 days overdue. Who can take care of this?

@parasharrajat
Copy link
Member

@kadiealexander Am I eligible for issue reporting bonus here?

@stitesExpensify
Copy link
Contributor

IMO that makes sense. You're tagged as the person who flagged it in the OP

@kadiealexander
Copy link
Contributor

Added a bonus to the Upwork Post for this issue: #5422 to avoid creating extra jobs. Thanks Rajat!

@kadiealexander
Copy link
Contributor

kadiealexander commented Oct 7, 2021

Also whipped up a job post to get @mananjadhav paid for the work done here, thanks Manan! I've invited you, please let me know when you've applied and I'll hire you, and pay out the job + bonus for the wait because of the n6-hold. https://www.upwork.com/jobs/~0199560da6fbed0b19

@MelvinBot
Copy link

@mananjadhav 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@MelvinBot
Copy link

@mananjadhav 10 days overdue. I'm getting more depressed than Marvin.

@mananjadhav
Copy link
Collaborator

PR is deployed to production

@MelvinBot MelvinBot removed the Overdue label Oct 11, 2021
@MelvinBot
Copy link

@mananjadhav Whoops! This issue is 2 days overdue. Let's get this updated quick!

@mananjadhav
Copy link
Collaborator

@kadiealexander Can you please help with this? PR is merged and into production 8 days back.

@MelvinBot MelvinBot removed the Overdue label Oct 15, 2021
@kadiealexander
Copy link
Contributor

kadiealexander commented Oct 18, 2021

Released payment, no bonus as this was not held for n6. :)

Edit: Spoke to Manan and as this was supposed to be held for n6 and was on hold for a month before merging, I'll still pay out the bonus here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants