https://bugs.kde.org/show_bug.cgi?id=486691
Bug ID: 486691
Summary: Content Warnings Are Not Preserved Upon Reply
Classification: Applications
Product: Tokodon
Version: 24.02.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: manif...@mindmesh.link
CC: c...@carlschwan.eu, j...@redstrate.com
Target Milestone: ---
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
SUMMARY
Replying to posts does not leave the same content warning as the parent post -
in fact, even if I manually turn on the CW field, it does not autofill the CW
from the thread.
STEPS TO REPRODUCE
1. Click reply on a post with a content warning
OBSERVED RESULT
Content warning is not inherited from replied-to post.
EXPECTED RESULT
Content warning should be inherited, at least optionally.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: NixOS 23.11
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
ADDITIONAL INFORMATION
This one's not a bug, more an opinionated default - but it's a default that
goes against the current Mastodon web UI, Tusky, Semaphore/Pinafore, and I'm
sure many other clients, so at the least, an option would be good for it. It's
expected behavior, and socially, many people bristle at having the warnings
accidentally removed from their posts, which an unsuspecting Tokodon user might
not know about, causing undue social friction.
--
You are receiving this mail because:
You are watching all bug changes.
