Stack compose form warnings and add a sensitive attachment hint to the compose form #29954
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.
This PR addresses both #29952 and #29953.
The compose form warning container is rewritten to order the various warnings in the following order of importance:
These warnings are now non-exclusive, meaning they render in a stack with all applicable warnings appearing. Previous behavior was that publicity-related disclaimers and warnings overwrote the hashtag warning.
Additionally, a sensitive attachment hint has been added to explain the "Add content warning" button's new functionality. This hint only appears if the post is marked with a content warning and the post has an attachment added.
(Please ignore the 10k character limit in the compose form. That's exclusive to my fork and entirely excluded from this PR.)