"Content warnings are matched case insensitively" is misleading
n
neocturne
started a topic
10 months ago
For the allow/hide filters to work, currently the CW must be written entirely in lowercase in the "filtered content warnings" settings (and will then match case insensitively for CWs on posts). If a CW added in the settings has any uppercase letters, it will not match anything, not even posts where the case of the CW is the same, which is quite confusing.
I came across the issue with acronyms which would usually be written in all-uppercase. I think it would make more sense if the words added in the settings where either handled fully case insensitively, or lower-cased when saving.
neocturne
For the allow/hide filters to work, currently the CW must be written entirely in lowercase in the "filtered content warnings" settings (and will then match case insensitively for CWs on posts). If a CW added in the settings has any uppercase letters, it will not match anything, not even posts where the case of the CW is the same, which is quite confusing.
I came across the issue with acronyms which would usually be written in all-uppercase. I think it would make more sense if the words added in the settings where either handled fully case insensitively, or lower-cased when saving.
1 person has this problem