[$500] [Taxes] User can access the background list using the arrow keys while the RHP is open

[lanitochka17]

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: 1.4.57-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: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to Paid workspace > Taxes
2. Open one tax setting
3. Press on the down and up arrow keys on the keyboard
4. Go back and go to categories settings
5. Open one category setting
6. Press on the down and up arrow keys on the keyboard

Expected Result:

Pressing on the arrow keys on the keyboard should do nothing as there is an RHP open

Actual Result:

Even if RHP is open pressing on the arrow keys moves through the background list

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6428753_1711549325149.bandicam_2024-03-27_17-18-00-957.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01008d99761a20e1bb
• Upwork Job ID: 1773361277524193280
• Last Price Increase: 2024-03-28
• Automatic offers:
• jayeshmangwani | Reviewer | 0
• ZhenjaHorbach | Contributor | 0

Issue Owner

Current Issue Owner: @CortneyOfstad

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[lanitochka17]

@CortneyOfstad FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[ZhenjaHorbach]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Taxes - User can access the background list using the arrow keys while the RHP is open

What is the root cause of that problem?

The main problem with the issue is that we do not process this case in any way when we're out of focus inside ArrowKeyFocusManager which we use for BaseOptionsSelector and BaseSelectionList

App/src/components/ArrowKeyFocusManager.js

Lines 79 to 83 in e87d35d

	onArrowUpKey() {
	if (this.props.maxIndex < 0) {
	return;
	}

What changes do you think we should make in order to solve the problem?

Since we only use this ArrowKeyFocusManager for lists, the best way to fix this is to make changes inside the manager to cover changes for both BaseOptionsSelector and BaseSelectionList

To fix this issue we can update ArrowKeyFocusManager and update condition onArrowUpKey and onArrowDownKey when we're out of focus

For this, we need to create a wrapper to get isFocused value for ArrowKeyFocusManager

function ArrowKeyFocusManager(props) {
    const isFocused = useIsFocused();

    return (
        <ArrowKeyFocusManagerBody
            isFocused={isFocused}
            {...props}
        />
    );
}

export default ArrowKeyFocusManager;

And then update conditions to disable onArrowUpKey and onArrowDownKey when we're out of focus

App/src/components/ArrowKeyFocusManager.js

Line 80 in e87d35d

if (this.props.maxIndex < 0) {

App/src/components/ArrowKeyFocusManager.js

Line 99 in e87d35d

if (this.props.maxIndex < 0) {

if (this.props.maxIndex < 0 || !this.props.isFocused) {

Plus we might want to reset the index offset state when we leave the screen
For this inside BaseOptionsSelector and BaseSelectionList we can set indexOffset as -1 when we leave the current screen using useEffect or componentDidUpdate (As alternative inside ArrowKeyFocusManager)

And if we want, we can always add an additional parameter that will make it possible to interact with lists when we are not in focus (But it doesn't make sense to me)

What alternative solutions did you explore? (Optional)

As an alternative, we can update onFocusedIndexChanged outside the manager
And just disable the index change function when we're out of focus

App/src/components/SelectionList/BaseSelectionList.tsx

Line 467 in 6690997

onFocusedIndexChanged={updateAndScrollToFocusedIndex}

App/src/components/OptionsSelector/BaseOptionsSelector.js

Line 617 in 3a61938

onFocusedIndexChanged={this.props.disableArrowKeysActions ? () => {} : this.updateFocusedIndex}

[shahinyan11]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Taxes - User can access the background list using the arrow keys while the RHP is open

What is the root cause of that problem?

We do not disable Arrow keys for SelectionList here

What changes do you think we should make in order to solve the problem?

1. Add const isFocused = useIsFocused(); here and add disableKeyboardShortcuts={!isFocused} prop to SelectionList

2. Update this line like below

maxIndex={disableKeyboardShortcuts ? -1 : slicedSections.flatMap((section) => section.data).length - 1}

We can add new disableArrowKeys prop to disable the arrow keys instead of using the disableKeyboardShortcuts so as not to use one prop to disable different actions

What alternative solutions did you explore? (Optional)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01008d99761a20e1bb

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (External)

[CortneyOfstad]

@jayeshmangwani we have some proposals for review above — thanks!

[CortneyOfstad]

Checking if this is VIP-VSP here