-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2024-08-29] [HOLD react-native-web 2584][$500] mWeb - Selecting and copying large name in share code displays remaining name with odd 3 dot position #27174
Comments
Triggered auto assignment to @johncschuster ( |
Job added to Upwork: https://www.upwork.com/jobs/~01fbd69c08b1d03d62 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @mallenexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
ProposalProblemmWeb - Selecting and copying large name in share code displays remaining name with odd 3 dot position Root causeWe are limiting the no. of line on Text for Display name. The behaviour of text component is to Scrolling while selecting on chrome and it truncates accordingly. ChangesWe can make the Display Name not selectable, by applying styles - userSelectNone or passing a prop userSelect="none" to text component as we already have a "copy to Clipboard link button" already |
@ishpaul777 Thanks for the proposal. I don't think your RCA is complete. Why the 3 dots do not change position (or get removed) and instead they stay in the same position they initially appeared at. |
I didn't check but initial thought is that the bug is not on Exp/App but in RNW or Chromium. |
ProposalPlease re-state the problem that we are trying to solve in this issue.mWeb - Although text is clipped and hidden user can still drag the selection cursor down to select the full text and the ellipsis is in the middle of the text. What is the root cause of that problem?ATM, we use The problem with Another problem is with What changes do you think we should make in order to solve the problem?Add |
@tienifr Thanks for the proposal. Your RCA makes sense. Regarding the |
Unassigning myself as BZ since I was the second one assigned. Let me know if you need help here @johncschuster |
@tienifr Thanks! Can you please update the PR with tests to follow RNW contributing guide |
Once I got assigned, I would submit a complete PR. That's just a draft PR for testing purpose. Correct me if I misunderstood something 🙇 |
🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @neil-marcellini, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Not overdue. Needs an engineer review here |
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:
|
|
Hi @johncschuster, is this issue eligible for reporting bonus? |
It looks like this issue was created September 11, 2023, and we removed the reporting bonus on October 24, 2023. I believe this issue should be eligible for the reporting bonus since it was reported before we removed the bonus. |
@dhanashree-sawant I've extended an offer to you, here. Can you please accept that? |
Thanks @johncschuster, I have accepted the offer. |
I've issued payment to @dhanashree-sawant 🎉 |
@johncschuster I was assigned this issue before moving to ND. This one should be paid through Upwork |
Oh! Thanks for that callout! I'll get a job going in a minute and ping you. |
Reopening until I've completed payment |
@johncschuster Accepted! Thanks! |
I've issued payment to @s77rt via Upwork. Thank you all for your contributions! 🎉 |
@johncschuster Same for me. Could you send an offer to me at https://www.upwork.com/freelancers/~01991fd5e5c11ef3ba? Thanks. |
(Reopening so I can handle the payment to @tienifr) |
@johncschuster hi I came to this issue from upwork and wondering if it's already taken up. |
📣 @opheliagame! 📣
|
@johncschuster Done, thanks! |
@opheliagame This issue is already handled but there are still plenty of issues that are open for proposals. Please checkout issues with |
I've issued payment to @tienifr. This is done! |
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:
Expected Result:
App should either not allow to extend name to select the full name on drag or should remove the 3 dots if name is extended and rest name is displayed
Actual Result:
App allows to extend name to display remaining name in share code and also keeps the 3 dots in same location on mWeb chrome
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.67.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
drag.and.extend.big.name.share.code.mp4
Screen_Recording_20230911_124133_Chrome.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694106668042179
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @johncschusterThe text was updated successfully, but these errors were encountered: