[HOLD] [$500] Web - Pressing the up arrow, the scroll bar is going down.

[kbecciv]

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:

1. Go to https://staging.new.expensify.com
2. Press the Tab key until the focus appears in Chat.

Expected Result:

When pressing the down arrow, the scrollbar should follow the down arrow command. When pressing the up arrow, the scrollbar should go up.

Actual Result:

When pressing the down arrow, the scroll bar is going up. When pressing the up arrow, the scroll bar is going down

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.1.54.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): n/a

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5523437_2022-04-07_10-42-59.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[Julesssss]

I can confirm this is occurring, but believe the real solution is to resolve this issue as this is a side effect of our current solution.

It also seems to occur regardless of using tabs. I can see the same issue just by clicking into the chat window, is that not the same for you @kbecciv?

[kbecciv]

@Julesssss There is another issue, we logged recently #8608. Is this the same issue?

[melvin-bot]

@Julesssss Eep! 4 days overdue now. Issues have feelings too...

[Julesssss]

@kbecciv that seems slightly different to me, lets keep both open.

[melvin-bot]

Triggered auto assignment to @trjExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[trjExpensify]

So @Julesssss, is this not a side effect of bidirectional scrolling as you mentioned here, or does it need to go on [hold] for now?

[Julesssss]

So I think this is a side effect yes, we can either put it on hold or just keep it open in the off chance that someone finds a fix outside of bi-directional scrolling. I'd lean towards the second option.

Also, the other mentioned issue is totally different IMO.