-
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
Profile - Phone number field is not auto focused #53030
Comments
Triggered auto assignment to @strepanier03 ( |
Edited by proposal-police: This proposal was edited at 2024-11-23 18:08:13 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Profile - Phone number field is not auto focused What is the root cause of that problem?
App/src/pages/settings/Profile/PersonalDetails/PhoneNumberPage.tsx Lines 96 to 111 in 3ebe852
What changes do you think we should make in order to solve the problem?Pass App/src/pages/settings/Profile/PersonalDetails/PhoneNumberPage.tsx Lines 96 to 111 in 3ebe852
Additionally we should check on other similar pages and and fix there too. What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Profile - Phone number field is not auto focused What is the root cause of that problem?We are not focusing the input here App/src/pages/settings/Profile/PersonalDetails/PhoneNumberPage.tsx Lines 96 to 111 in 3ebe852
What changes do you think we should make in order to solve the problem?We can use App/src/pages/GroupChatNameEditPage.tsx Line 110 in 3ebe852
and here
const {inputCallbackRef} = useAutoFocusInput();
<InputWrapper
InputComponent={TextInput}
inputID={INPUT_IDS.PHONE_NUMBER}
name="lfname"
label={translate('common.phoneNumber')}
aria-label={translate('common.phoneNumber')}
role={CONST.ROLE.PRESENTATION}
defaultValue={phoneNumber}
spellCheck={false}
// inputCallbackRef
ref={inputCallbackRef}
onBlur={() => {
if (!validateLoginError) {
return;
}
PersonalDetails.clearPhoneNumberError();
}}
/> What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Profile - Phone number field is not auto focused What is the root cause of that problem?We do not handle autofocus for private profile fields such as phone number, legal name, and address. Phone number: App/src/pages/settings/Profile/PersonalDetails/PhoneNumberPage.tsx Lines 96 to 111 in e532ef1
Legal name: App/src/pages/settings/Profile/PersonalDetails/LegalNamePage.tsx Lines 101 to 110 in 44b2f77
Address still does not autofocus, but since it uses a different component, we can report and update it later App/src/components/AddressForm.tsx Lines 148 to 166 in 2c27e63
What changes do you think we should make in order to solve the problem?To resolve this, we will add Phone number: App/src/pages/settings/Profile/PersonalDetails/PhoneNumberPage.tsx Lines 96 to 111 in e532ef1
autoFocus
shouldDelayFocus={shouldDelayFocus} Legal name: App/src/pages/settings/Profile/PersonalDetails/LegalNamePage.tsx Lines 101 to 110 in 44b2f77
autoFocus
shouldDelayFocus={shouldDelayFocus} POCScreen.Recording.2024-11-24.at.22.18.28.movWhat alternative solutions did you explore? (Optional) |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: v9.0.66-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): gibethlehem@gmail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The phone number field is auto-focused.
Actual Result:
The phone number field is not auto-focused.
The same behavior with the Legal name and Address pages.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Screenshots/Videos
Bug6673771_1732326370020.23.11.2024_04.31.34_REC.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: