[codex] Fix Firefox message reply overflow and other compose area issues#2744
Draft
guaka wants to merge 7 commits into
Draft
[codex] Fix Firefox message reply overflow and other compose area issues#2744guaka wants to merge 7 commits into
guaka wants to merge 7 commits into
Conversation
added 2 commits
June 20, 2026 19:04
E2E screenshotsRun: messages-firefox-layout-reply editor remains usable when long text overflowssetup-authenticated-create admin storage statesetup-authenticated-create authenticated storage statesetup-authenticated-create seeded member storage state |
Coverage overviewStatus: Passing
End-to-end areas
Full HTML overview: download the |
Contributor
Author
|
we might as well want to fix other stuff related to the compose area
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




What changed
Fixes #2722
Validation
npm run test:client -- ThreadReplybash -n scripts/e2e/test-e2e.shnpx eslint modules/messages/client/components/Thread.component.js modules/messages/client/components/ThreadMessages.js modules/messages/client/components/ThreadReply.js playwright.config.js tests/e2e/test.js tests/e2e/messages-layout.spec.jsTRUSTROOTS_E2E_SKIP_COVERAGE_REPORT=true npm run test:e2e -- --project=messages --project=messages-firefox-layout --grep "reply editor remains usable"Notes
messages-firefox-layouttest and the existingmessagesproject passed, but the full run ended with unrelated public/auth/member failures and laterENOSPC: no space left on deviceerrors after generating large Playwright artifacts locally.