Repository navigation
Mark down - Position of text with header and line changes after collapsing the composer #39271
Description
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.58-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38152
Issue reported by: Applause - Internal Team
Action Performed:
- Go to staging.new.expensify.com
- Go to chat.
- Type # header.
- Hit Enter to create a new line.
- Note the position of text in the composer.
- Expand the composer.
- Collapse the composer.
Expected Result:
The position of text in the composer after expanding and collapsing the composer should be the same as the position before expanding the composer.
Actual Result:
After expanding and collapsing the composer, the text in the composer becomes top-aligned.
Workaround:
n/a
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
Activity
melvin-bot commentedon Mar 29, 2024
Triggered auto assignment to @hayata-suenaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.kbecciv commentedon Mar 29, 2024
We think that this bug might be related to #vip-vsb
github-actions commentedon Mar 29, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
hayata-suenaga commentedon Mar 29, 2024
I don't believe this is a bug 😄 The added header is the first line of the text. It should remain so even when the composer is expanded.