-
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 #23757][$1000] Web - LHN - Emoji picker doesn't close when navigating to other chat with the browser back button #24559
Comments
Triggered auto assignment to @kadiealexander ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - LHN - Emoji picker doesn't close when navigating to other chat with the browser back button What is the root cause of that problem?We haven't had any logic to hide the EmojiPicker when the current report is unmount and mount another report What changes do you think we should make in order to solve the problem?I think we can put logic to hide the EmojiPicker when the report action compose is unmounted. That means, in the componentWillUnmount of ReportActionCompose, we can call Beside that, with new implement in this PR #24479, before call EmojiPickerActions.hideEmojiPicker, we can check if the EmojiPicker is active for current reportID |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - LHN - Emoji picker doesn't close when navigating to other chat with the browser back button What is the root cause of that problem?When What changes do you think we should make in order to solve the problem?Add code to hide const {currentReportID} = useCurrentReportID();
useEffect(() => {
if (!EmojiPickerAction.emojiPickerRef.current || !EmojiPickerAction.emojiPickerRef.current.isEmojiPickerVisible) return;
EmojiPickerAction.emojiPickerRef.current.hideEmojiPicker();
}, [currentReportID]) What alternative solutions did you explore? (Optional)N/A |
This comment was marked as outdated.
This comment was marked as outdated.
@Natnael-Guchima I'm having a lot of trouble following your reproduction steps. It looks like, from the video, you're logged into two accounts. Can you please write more detailed steps that make it clear which user and tab to use? |
@kadiealexander No need for two accounts to reproduce.
|
@kadiealexander please try the steps listed below, and let me know if you are not able to reproduce the issue. Action Performed:
Expected Result: Screencast.from.2023-08-16.09-37-57.mp4 |
I can't reproduce on the latest version: 2023-08-16_19-20-13.mp4@Natnael-Guchima could you please test on version v1.3.54-11 and let me know if you're still experiencing it? |
I am still able to reproduce it on the latest version (v1.3.54-11). I am not sure if this is a device-specific issue. @ShogunFire are you able to reproduce this on that latest release? Screencast.from.2023-08-16.10-43-41.mp4 |
@Natnael-Guchima are you testing on Windows? It's possible it's windows-specific. |
Yes, I am testing on windows. |
Also testing on windows |
I can reproduce this on staging (v1.3.54-11) and production (v1.3.53-2) |
What device are you testing on? Is it Mac or Windows? @jfquevedol2198 |
MacOS / Chrome |
@Natnael-Guchima I can also reproduce this on Windows |
I was able to repro this morning on Mac Chrome v1.3.54-13. |
Job added to Upwork: https://www.upwork.com/jobs/~01a49af3096640d7b0 |
Current assignee @kadiealexander is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ArekChr ( |
This might be fixed in #23757 so let's put this on hold for now |
@kadiealexander this issue is fixed on dev now. The fixing PR is here which was intended to fix another issue that was reported here. The discussion to fix this issue - the one I reported - on the fixing PR starts here on Aug 15, and I reported this issue on Aug 5. On Aug 15, a new solution was introduced here to fix the issue I reported:
This is to ask if I am eligible for reporting bonus since the discussion to fix the issue I reported comes after I reported the issue? The issue fixed on dev: Screencast.from.2023-08-25.09-27-18.mp4The current behavior of the issue on the latest staging. Screencast.from.2023-08-25.09-30-20.mp4My reporting date |
@Natnael-Guchima I don't think we typically pay out reporting bonuses for issues that were fixed elsewhere. Generally if something goes on hold because another PR will fix it, we don't make any payments when it comes off hold and is fixed. Sorry about that! |
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:
Emoji picker should either close on navigating to other chat or the selected emoji should be entered to the current composer
Actual Result:
Emoji picker doesn't close & selecting emoji inserts emoji user B's composer
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.54-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
Screencast.from.2023-08-04.23-56-31.mp4
Recording.1194.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691182964868429
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: