You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[No payment] Mark down - Message is centered when editing message #82095
Version Number: 9.3.17-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#81018 Email or phone of affected tester (no customers):sjiondjsondjoisjsojdos@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Money Requests
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug (App) Causing PR: Unable to identify with high confidence Current Status: Needs Investigation
Recommendation: NEEDS INVESTIGATION
The issue reports that messages are centered instead of left-aligned when editing. While the issue was discovered during regression testing of PR #81018 (emoji code block handling), my investigation found that #81018 did not modify any styling or alignment code - it only changed emoji replacement logic in EmojiUtils.tsx and SuggestionEmoji.tsx.
The bug is only reproducible on staging, not production, which confirms it was introduced by a PR in the current deploy (9.3.17-0). However, after reviewing the modified files in #81018 and checking recent changes to ReportActionItemMessageEdit.tsx (the component responsible for editing messages), I could not find any obvious styling changes that would cause centering.
Labels: No label changes made. Keeping both DeployBlockerCash and DeployBlocker until root cause is identified.
@TaduJR@mitarachim - Can you help clarify which specific PR introduced this issue? The regression was found while testing #81018, but that PR does not contain styling changes that would cause this alignment bug.
@inimaga@lydiabarclay The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Weird edge case here, payment won't be due here so we'll sort elsewhere if needed. thx
actually... @situchan, might you be due compensation for helping to find the offending PR? We don't have a normal process for that but you mentioned it took you a while and you found #82124 too.
It's true that this was hard investigation to find the offending PR. @mallenexpensify I'll defer to you whether I am eligible payment or not. I am fine either way. Thanks
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Thanks @situchan , we appreciate the help here. I don't want to set precedence for paying to help find regressions, especially right now with a lot of changes happening, so I'm going to close this out and ping you 1:1 about summin. Thanks again
changed the title [-][Due for payment 2026-02-20] Mark down - Message is centered when editing message[/-][+][No payment] Mark down - Message is centered when editing message[/+]on Feb 20, 2026
Activity
melvin-bot commentedon Feb 11, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #81018
melvin-bot commentedon Feb 11, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 11, 2026
Triggered auto assignment to @lydiabarclay (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Feb 11, 2026
👋 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:
OSBotify commentedon Feb 11, 2026
Investigation Summary
Classification: Frontend bug (App)
Causing PR: Unable to identify with high confidence
Current Status: Needs Investigation
Recommendation: NEEDS INVESTIGATION
The issue reports that messages are centered instead of left-aligned when editing. While the issue was discovered during regression testing of PR #81018 (emoji code block handling), my investigation found that #81018 did not modify any styling or alignment code - it only changed emoji replacement logic in
EmojiUtils.tsxandSuggestionEmoji.tsx.The bug is only reproducible on staging, not production, which confirms it was introduced by a PR in the current deploy (9.3.17-0). However, after reviewing the modified files in #81018 and checking recent changes to
ReportActionItemMessageEdit.tsx(the component responsible for editing messages), I could not find any obvious styling changes that would cause centering.Evidence
EmojiUtils.tsx,SuggestionEmoji.tsx, and test files onlyReportActionItemMessageEdit.tsx,styles/index.ts(for chat message styles), or any alignment-related codestyles.chatItemMessageandstyles.flexRowat line 487Next Steps
chatItemMessage,flexRow,chatItemComposeBox, ortextInputComposestylesLabels: No label changes made. Keeping both
DeployBlockerCashandDeployBlockeruntil root cause is identified.@TaduJR @mitarachim - Can you help clarify which specific PR introduced this issue? The regression was found while testing #81018, but that PR does not contain styling changes that would cause this alignment bug.
25 remaining items
melvin-bot commentedon Feb 13, 2026
@inimaga @lydiabarclay The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
brianlee-expensify commentedon Feb 19, 2026
payment still needs to be made for this, reopening (CC @lydiabarclay)
@mallenexpensify would love your thoughts on the payments for the following GHs:
lydiabarclay commentedon Feb 19, 2026
Pinged in Slack
mallenexpensify commentedon Feb 20, 2026
Weird edge case here, payment won't be due here so we'll sort elsewhere if needed. thx
actually... @situchan, might you be due compensation for helping to find the offending PR? We don't have a normal process for that but you mentioned it took you a while and you found #82124 too.
hmmm
situchan commentedon Feb 20, 2026
It's true that this was hard investigation to find the offending PR.
@mallenexpensify I'll defer to you whether I am eligible payment or not. I am fine either way. Thanks
melvin-bot commentedon Feb 20, 2026
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
mallenexpensify commentedon Feb 20, 2026
Thanks @situchan , we appreciate the help here. I don't want to set precedence for paying to help find regressions, especially right now with a lot of changes happening, so I'm going to close this out and ping you 1:1 about summin. Thanks again
[-][Due for payment 2026-02-20] Mark down - Message is centered when editing message[/-][+][No payment] Mark down - Message is centered when editing message[/+]situchan commentedon Feb 26, 2026
App/src/pages/inbox/report/PureReportActionItem.tsx
Line 2071 in b46dee1
A bit late but the offending line (which caused 2 regressions) also caused another regression:
#37447 (comment)
This should have been reverted.