Padding seems off for the latest message with the typing indicator moved to the top

[mvtglobally]

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. Open any chat
2. check padding below last chat and compose box

Expected Result:

We should have the metadata above and below the compose box as before and make sure it is vertically aligned. Decided in Slack here.

Actual Result:

Padding seems too high for the latest message with the typing indicator moved to the top

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web

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

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

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[mountiny]

I could find that this is related to two PRs recently

• first this: Move all the compose meta data to be above the compose input #9095 cc @tgolen was ooo for a while
• then Fix spacing in compose metadata #9206 cc @amyevans

I dont think this needs to be a deploy blocker since it is mainly a small styling problem.

[mountiny]

Sorry @arielgreen for the ping, I will actually wait to first refine how it should look like exactly and all the expected behaviours as there seems to be some discussion about it in the Slack thread.

[mountiny]

Making this weekly for now, we need to find some consensus on what would be the best way to render these.

from #9205

[mountiny]

Asked in Slack here, giving it some time.

We would like to get it close to this state #9094, but I will try to keep the refacotring that Tim has introduced in here #9095