[HOLD #11795] [$250] Invite new members to workspace text-input is not focused - Reported by @aneequeahmad

[mvtglobally]

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:

1. Click on use icon to open setting page.
2. Click on workspace > manage members > invite .

Expected Result:

Search field of invite new members should be focused.

Actual Result:

Search field is not focused

Workaround:

unknown.

Platform:

Where is this issue occurring?

• Web
• Desktop App

Version Number: 1.1.91-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2022-08-25.at.7.31.24.PM.mov

Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1661437929132899

View all open jobs on GitHub

[melvin-bot]

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

[varshamb]

Proposal

In WorkspaceInvite page autoFocus for OptionsSelector is false. Making it true will fix this issue.

App/src/pages/workspace/WorkspaceInvitePage.js

Lines 249 to 250 in 386c5ad

	<OptionsSelector
	autoFocus={false}

[neil-marcellini]

Closing this because that's the expected behavior. See my slack comment here. If we agree it's a bug in the future then we can re-open this.

[neil-marcellini]

Re-opening because the Slack discussion is ongoing and there's some good points there.

[neil-marcellini]

I think this would be a good external issue, but we should hold on implementation until we decide what to do in Slack.

[melvin-bot]

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

[zanyrenney]

@neil-marcellini it looks like we landed on doing nothing for now. Please can you confirm your thoughts as you said hold until we decide in slack... Thanks!

[zanyrenney]

oops! didn't mean to close with that comment.

[neil-marcellini]

I don't think we have talked about it anymore since then. I don't see anything from a quick Slack search. We could close this or make it Monthly again.

[mountiny]

Checked in with Zany on this one, it is an old issue and not reproducible in staging/prod anymore so we are good to close it 🎉

[neil-marcellini]

Ditto

[neil-marcellini]

Holding still

[neil-marcellini]

#11795 is being actively worked on, we're still holding here.

[neil-marcellini]

Same update

[neil-marcellini]

Still on hold, but there's progress on the issue.

[zanyrenney]

Still on hold, latest is here- #11795

[zanyrenney]

Still on hold, latest is here- #11795

[neil-marcellini]

@zanyrenney This has already been fixed. It was brought to my attention in Slack here, and after testing it I can confirm it's fixed.

Screen.Recording.2023-10-10.at.12.40.38.PM.mov

[zanyrenney]

As per @neil-marcellini comment above, and the fix being handled elsewhere, closing this one out!

[aneequeahmad]

@zanyrenney i think reporting bonus payment is yet to be paid for this issue.

[aneequeahmad]

@zanyrenney any update on the payment?

[aneequeahmad]

@zanyrenney Just a friendly reminder. Bug reporter payment is still pending for this issue.