Observed behaviour
- At step 6, no custom warning appears. Instead, it seems accepting the warning at the community-level implies accepting all channel-specific warnings, which may be correct for strictly accepting an NSFW agreement but probably should not apply when custom warnings are set.
- After completing step 7, the right-click option to "Reset mature content agreement state" remains at the community level, which after poking and prodding makes sense but is a bit unexpected.
Reproduction steps
- Create a brand new community
- Go to community settings > Safety & Moderation > Mark this community for mature content and enable the setting
- Accept the mature content warning
- Edit #general and set it for Mature Content
- Add some Custom warning text
- Note no custom warning appears
- Edit the community settings to NOT be marked for mature content
Build information
Canary 779 (8122e4d), Host 0.0.223, Linux 7.0.7-100.fc43.x86_64 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-US
Platform
Linux
Details
Expected behaviour
- In step 6, if a custom warning is set for a channel in a community that already has a content warning, whether custom or not, the more specific context should take precedent so the channel's specific warning should appear.
- After completing step 7, the "Reset mature content agreement state" option should appear on individual channels, rather than at the community.
1 comment
Comment by Hampus