-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 #37437][$2000] Pressing space
2 times .
appears in display name
#17153
Comments
Triggered auto assignment to @Christinadobrzyn ( |
Bug0 Triage Checklist (Main S/O)
|
@Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Thanks @PrashantMangukiya! I'll reach out in the slack chat to see if we can do some more testing - https://expensify.slack.com/archives/C049HHMV9SM/p1681247093995989?thread_ts=1680851400.066889&cid=C049HHMV9SM |
did some testing and updated the OP - asking for a quick review to make sure I understand correctly - https://expensify.slack.com/archives/C049HHMV9SM/p1681334171519149?thread_ts=1680851400.066889&cid=C049HHMV9SM |
space
3 times .
appears in display namespace
3 times .
appears in display name
Job added to Upwork: https://www.upwork.com/jobs/~0194127eb40345b2ea |
Current assignee @Christinadobrzyn is eligible for the External assigner, not assigning anyone new. |
Updated OP based on Slack chat - I think this can be External. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
Triggered auto assignment to @chiragsalian ( |
@chiragsalian, @Christinadobrzyn, @0xmiroslav Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Looks like we're waiting on more proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
space
3 times .
appears in display namespace
3 times .
appears in display name
Upwork job price has been updated to $2000 |
Hey, I will ping today, still no news. I created another issue related with TextInput, if that one get attention I will try to mention this one, so maybe it gets some momentum again. |
Hi @gedu just checking in on this for an update - thank you! |
Hey, no yes, I pinged less of 2 weeks ago, but no response. I will try on Discord |
Hey, I wrote on Discord trying to call my PR attention, still no news |
Thanks @gedu , we've def found that upstream fixes can take a while. |
I sent another ping to the reviewer |
Posting my PR on these thread to see if it can get some visibility: https://x.com/dan_abramov2/status/1842513065952354438 |
Also noticed @mrousavy from Margelo commented there. We work with them in case that's relevant or helpful. :) |
lol, this is exactly what we talked about yesterday @hannojg. |
Seems that got some traction, the reviewer is taking a look, I will fix the conflicts and clean up a bit the code: facebook/react-native#39385 (comment) |
I just updated the PR, solved the conflicts, tomorrow I have to fix some examples I think |
I fixed some examples that changed after a merge conflict |
Nick made a fix, that I think is related with mine, his handle on a more generic way, we should test if this bug is still happening after his fix, So I will close my PR |
So we will just have to update to the version of react native that contains this PR, right? |
@AndrewGable yes @Christinadobrzyn not sure what should be the next step for this issue |
Unfortunately this issue does not seem to be resolved with the patch in facebook/react-native#39385 (review) as reported in facebook/react-native#27693 (comment). I may have messed something up, but I tried using patch-package to apply the patch. The patch definitely compiles, but there is no behavior change and the bug persists in New Arch. |
📣 @mhoran! 📣
|
With all the patches mentioned in reactwg/react-native-releases#595 (comment), this issue should be resolved once and for all. The pick request should result in these patches making their way into a future 0.76 release. In the meantime, you can apply the patches manually atop 0.76 as shown in the reproducer. |
Just checking on this, I'm not sure what we should do here. @mhoran @eVoloshchak @gedu should we continue to keep this on hold for the patch? |
The patch landed in React Native v0.76.2. Note that the app must be moved to the New Architecture, as the fix was only implemented for New Architecture. |
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:
if "." shortcut is enabled, the shortcut should work when tapping the space 2 times
Actual Result:
if "." shorcut is enabled, the shortcut doesn't work when tapping the space 2 times
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.96-4
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
m.web.safari.mp4
ios.app.mp4
TWPP4035.1.MP4
Expensify/Expensify Issue URL:
Issue reported by: @harshad2711
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680851400066889
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: