Fix compose form behavior in mobile view #15555
Merged
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.
Fixes #13094
Until this PR, when writing toots in mobile view, two
ComposeForm
components were rendered:/web/statuses/new
pathThe auto-focus and auto-selection code was executed on the hidden
ComposeForm
(causing a crash in PaleMoon, see #13094) and wasn't executed on the displayedComposeForm
component.This PR uses media queries to decide whether to render the compose pane's
ComposeForm
, avoiding unnecessary rendering the hidden component and avoiding the PaleMoon crash, and makes it so the auto-selection and auto-focus code gets executed when replying to toots in mobile view.