-
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 2023-08-03] [$1000] Emoji picker's position changes on decreasing the screen size #17603
Comments
Triggered auto assignment to @sophiepintoraetz ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
This is not an issue but expected behaviour due to the screen resizing. |
Hey Sophie! The first video in the OP is the one that shows the bug. The emoji picker jumps to the LHN instead of behaving the correct way (as in the second video). This was also reported here but I'm reopening this one instead to ensure the original bug reporter is credited. |
ProposalPlease re-state the problem that we are trying to solve in this issue.The emoji picker positions itself to the top-left corner of the screen if the window dimensions change. What is the root cause of that problem?The anchor referenced by App/src/components/EmojiPicker/EmojiPicker.js Lines 42 to 46 in 5a713dd
This causes the position to be x=0, y=0. What changes do you think we should make in order to solve the problem?We need to use the same anchor that is used by What alternative solutions did you explore? (Optional)N/A Originally posted by @samh-nl in #21982 (comment) |
Job added to Upwork: https://www.upwork.com/jobs/~019f4f66f49e6e10ed |
Current assignee @sophiepintoraetz is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
Thanks, @kadiealexander - that description helped!
|
ProposalPlease re-state the problem that we are trying to solve in this issue.What is the root cause of that problem?This is caused by this line where we are checking if device is touchscreen and medium size, if so we are removing emoji picker button App/src/pages/home/report/ReportActionCompose.js Line 1123 in ecfcd83
Thus when this button disappears emoji picker popover will lose it is target position What changes do you think we should make in order to solve the problem?I am not sure about this line: App/src/pages/home/report/ReportActionCompose.js Line 1123 in ecfcd83
It is not logical to me, for example in mid sized tablets we do not show emoji picker button, how are they going to use it then? This is image of ipad mini in chrome responsive mode I think we should remove this condition and want to show emoji picker button always. What alternative solutions did you explore? (Optional)Also we can hide emoji picker if anchor element is unmounted. I checked if We can check if element is visible and if not we can hide emoji picker, like this: if (!emojiPopoverAnchor.current.checkVisibility()) {
hideEmojiPicker(false);
return;
} |
ProposalPlease re-state the problem that we are trying to solve in this issue.Emoji picker's position changes on decreasing the screen size What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?To fix this issue #21982 as well. I think we can expose another method called clearEmojiPopoverAnchor here and call this method inside Then in window size change callback, we check if emojiPopoverAnchor.current is cleared, we skip recalculate its position and hide the emoji picker. What alternative solutions did you explore? (Optional)I think if the useEffect(() => () => {
EmojiPickerAction.hideEmojiPicker()
}, []); Result: Screen.Recording.2023-07-10.at.23.25.58.mp4 |
Just waiting on @allroundexperts to review! |
I can't reproduce this @sophiepintoraetz. Can you please confirm? |
@allroundexperts You have to simulate in responsive mode of chrome, this issue is reproducible only in medium sized screen and touchscreen enabled |
@alitoshmatov Can you please share a video of how you're reproducing this behaviour? |
Screen.Recording.2023-07-06.at.11.38.11.AM.mov |
Thanks @alitoshmatov! |
@alitoshmatov's proposal looks good to me. @sophiepintoraetz We can either hide the emoji picker menu when the button is hidden OR we can make the button always visible. I prefer to hide the emoji picker menu when the button gets hidden instead of showing the button always. @sophiepintoraetz Can you please confirm the expected behaviour here? In either case, @alitoshmatov's proposal works well. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @Li357, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@allroundexperts @Li357 Thanks for accepting my proposal. The PR is ready #22792. Please help me review it. Thanks |
@hoangzinh, @Li357, @allroundexperts, @sophiepintoraetz Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Still in review. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.46-2 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 2023-08-03. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
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:
|
Checklist
|
Payouts due (I believe the date for the bonus calculation is correct): Issue Reporter: $250 @daraksha-dk Eligible for 50% #urgency bonus? N (penalty applied) |
@sophiepintoraetz could we consider again the penalty in this case? Reasons:
|
@hoangzinh I appreciate the ask but I do not think that's fair to other individuals who submitted proposals and could have completed this job/other contributors who have been penalised for the same reasons. I am glad that you were thorough but we do make the guidelines clear - I would suggest taking more care in your original proposal! |
I would agree with @sophiepintoraetz on this one. Though just for record, it did not take 14 working days to get this merged. This was merged within 9 days (excluding the weekends). |
@allroundexperts - sorry - I used a calculator which I thought was accurate, you're right in that it wasn't 14 days but am I correct in saying that there are 10 days between assignment and merging? |
I used this to calculate the exact period. This is pretty accurate AFAIK. |
Got it. Moot point seeing as we're in agreement but I appreciate the accuracy. Reconfirming that the payments will be |
Offers sent to @daraksha-dk and @hoangzinh |
Accepted the offer. Thanks @sophiepintoraetz |
1 similar comment
Accepted the offer. Thanks @sophiepintoraetz |
Payments done - @allroundexperts - just drop the request here when you're ready! |
Requested. Thanks! |
Reviewed the above payment details for @allroundexperts. This is approved for payment in NewDot. |
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:
Expected Result :
The emoji picker jumps to the LHN instead of behaving the correct way (as in the second video).
Actual Result :
Emoji picker's position changes
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?
Version Number: 1.3.1
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
Current:
Screen.Recording.2023-04-18.at.12.31.19.AM.mov
Expected:
Recording.270.mp4
Expensify/Expensify Issue URL:
Issue reported by: @daraksha-dk
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681758191524309
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: