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

[HOLD for payment 2022-12-20] [$8000] iOS Safari - Blue text selection persists in the compose box even after message is sent @metehanozyurt #8592

Closed
kbecciv opened this issue Apr 11, 2022 · 168 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering Improvement Item broken or needs improvement. Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review

Comments

@kbecciv
Copy link

kbecciv commented Apr 11, 2022

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:

In iOS Settings, Go to General > Keyboard and enable autocorrection

  1. Go to https://new.expensify.com on Safari iOS
  2. Log in with any account and select any chat
  3. Enter incorrectly spelled word in the compose box and let the autocorrection warn you with the blue text selection.
  4. Send the message

Expected Result:

Compose box should be cleared and empty blue selection shouldn't persist.

Actual Result:

Blue text selection still exist.

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Mobile Web (safari)

Version Number: 1.1.92.0 (Matt A retested 8/26/22)

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): n/a

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

Notes/Photos/Videos: Any additional supporting documentation

1.mp4
2.mp4

Expensify/Expensify Issue URL:

Issue reported by: @metehanozyurt

Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1648452635209129

View all open jobs on GitHub

@kbecciv kbecciv added the AutoAssignerTriage Auto assign issues for triage to an available triage team member label Apr 11, 2022
@melvin-bot
Copy link

melvin-bot bot commented Apr 11, 2022

Triggered auto assignment to @cdraeger11 (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed AutoAssignerTriage Auto assign issues for triage to an available triage team member labels Apr 11, 2022
@melvin-bot
Copy link

melvin-bot bot commented Apr 14, 2022

@cdraeger11 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@melvin-bot
Copy link

melvin-bot bot commented Apr 18, 2022

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

@melvin-bot
Copy link

melvin-bot bot commented Apr 20, 2022

@cdraeger11 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

@cdraeger11 cdraeger11 removed their assignment Apr 20, 2022
@melvin-bot melvin-bot bot removed the Overdue label Apr 20, 2022
@melvin-bot
Copy link

melvin-bot bot commented Apr 20, 2022

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

@MonilBhavsar MonilBhavsar added the Improvement Item broken or needs improvement. label Apr 21, 2022
@MonilBhavsar
Copy link
Contributor

Can't seem to reproduce on Safari web, but can reproduce on iOS simulator

@MonilBhavsar MonilBhavsar changed the title mWeb/safari - When send request correction blue background will not remove @metehanozyurt iOS - When send request correction blue background will not remove @metehanozyurt Apr 21, 2022
@MonilBhavsar
Copy link
Contributor

Asked for confirmation on a PR which I think caused this.

@parasharrajat
Copy link
Member

Looked at the issue. Tried a few things to see if those fix it but no luck. I will try more tomorrow.

@melvin-bot melvin-bot bot added the Overdue label Apr 25, 2022
@melvin-bot
Copy link

melvin-bot bot commented Apr 26, 2022

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

@MonilBhavsar
Copy link
Contributor

Will get back to this

@melvin-bot melvin-bot bot removed the Overdue label Apr 28, 2022
@MonilBhavsar
Copy link
Contributor

@parasharrajat since this seems like a regression, do you want to give it a try to fix this?

@parasharrajat
Copy link
Member

I would be happy to do that but I have been preoccupied with other stuff. I will try to debug this over the weekend and let you know by Monday.

@melvin-bot melvin-bot bot added the Overdue label May 2, 2022
@MonilBhavsar MonilBhavsar added Weekly KSv2 and removed Daily KSv2 labels May 2, 2022
@melvin-bot melvin-bot bot removed the Overdue label May 2, 2022
@MonilBhavsar
Copy link
Contributor

PR is on staging

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Dec 13, 2022
@melvin-bot melvin-bot bot changed the title [$8000] iOS Safari - Blue text selection persists in the compose box even after message is sent @metehanozyurt [HOLD for payment 2022-12-20] [$8000] iOS Safari - Blue text selection persists in the compose box even after message is sent @metehanozyurt Dec 13, 2022
@melvin-bot
Copy link

melvin-bot bot commented Dec 13, 2022

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.38-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2022-12-20. 🎊

After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Dec 13, 2022

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Dec 20, 2022
@mallenexpensify
Copy link
Contributor

Hi all, this is a 🐯 of an issue (over 200 comments) and we need to suss out payments.

  1. @parasharrajat are you able to help?
  2. If so... have you been assigned since the beginning, looks like it? (asking cuz, if you've invested time all along, include reviewing the PR, I imagine your compensation rate would be higher.)
  3. If yes to the above, and you've invested a considerable amount of time, is there any reason you wouldn't/shouldn't be due the original $8000 job price?
  4. Here's where things might get tricky. We made this issue internal, @MonilBhavsar and @parasharrajat , did we use a substantial amount of code from any previously submitted proposals? If so, can you link to them, tag the contributor and guesstimate how much of their code you used? (in increments of 25%, 50% or ~100%).
  5. Once we have details from Moving files and folders a little #4 we'll work on potential compensation amounts.

@parasharrajat
Copy link
Member

did we use a substantial amount of code from any previously submitted proposals?

@mallenexpensify I am discussing that @MonilBhavsar and I will let you know.

If so... have you been assigned since the beginning, looks like it? (asking cuz, if you've invested time all along, including reviewing the PR, I imagine your compensation rate would be higher.)

I am happy to go with the existing process and thus no need to go higher than the eligible amount.

@mallenexpensify
Copy link
Contributor

have you been assigned since the beginning, looks like it? (asking cuz, if you've invested time all along, including reviewing the PR, I imagine your compensation rate would be higher.)

@parasharrajat, what I meant here is, assuming we have the option for payments of $1000k (standard), 100%, 50% and 25% of the job amount. I'm suggesting that your pay would be in the higher bracket.

Let me know when you and @MonilBhavsar reach consensus on if any code was used. Thx

@parasharrajat
Copy link
Member

@mallenexpensify I think proposal should be eligible for some compensation. Although, it was rejected initially because we wanted to solve the main issue instead of disabling the feature at that time, the ultimate changes that were done to close this issue match with the approach in that proposal.

So in good faith and as per our policy, I think we can pay 25% to @songlang1994 which was the first to propose it.

A lot of research and investigation was done on other proposals but none of them was implemented. We decided to take it internal for competing with internal priorities. Considering the urgency of WAQ, and very fewer users affected by the bug, we decided to disable the feature and close this issue.

@mallenexpensify
Copy link
Contributor

Thanks @parasharrajat
Can I get one... last... final confirmation from @MonilBhavsar and @parasharrajat before I pay?

  • @parasharrajat $8000 for proposals and PR review
  • @songlang1994 $2000 for 25% compensation for code submitted that ended up being used.

Sound good?!?!?
Please apply and I'll get paid once we confirm
https://www.upwork.com/jobs/~019b27cbf20756346d

@mallenexpensify
Copy link
Contributor

@MonilBhavsar ping for confirmation on the above when you're back. Thx

@MonilBhavsar
Copy link
Contributor

This plan looks good to me 👍

@mallenexpensify
Copy link
Contributor

Thanks @MonilBhavsar
@parasharrajat can you please accept the job and reply here once you have?
@songlang1994 please apply and confirm when you have.
https://www.upwork.com/jobs/~019b27cbf20756346d

@metehanozyurt
Copy link
Contributor

@mallenexpensify May I have the reporting bonus for this one?

@arielgreen
Copy link
Contributor

@metehanozyurt yes; can you please apply to the job?

@arielgreen
Copy link
Contributor

@parasharrajat payment issued.

@metehanozyurt
Copy link
Contributor

I applied, thank you @arielgreen .

@arielgreen
Copy link
Contributor

Also sent offer to @songlang1994

@songlang1994
Copy link
Contributor

Offer accepted. Thank you @arielgreen

@arielgreen
Copy link
Contributor

Excellent, all parties have been paid.

@arielgreen
Copy link
Contributor

@parasharrajat @MonilBhavsar can you please review the checklist?

@MonilBhavsar
Copy link
Contributor

Done!

@arielgreen
Copy link
Contributor

Thank you! Reviewing adding a regression test to this, then we'll be set to close it out.

@arielgreen
Copy link
Contributor

Proposed test here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering Improvement Item broken or needs improvement. Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review
Projects
None yet
Development

No branches or pull requests