Spaces ignored when deciding how to censor a word.
JamieRCHI opened this issue · comments
🐛 Description
With 'omg' censored, 'om g' is changed to 'xxx'.
🔀 Steps To Reproduce
- Add 'omg' to the words to be censored.
- Enable replace with 'xxx'.
- Refresh this page and look at my comments.
✔️ Expected behavior
I should see 'from growing' not 'frxxxrowing'.
I would expect your code to Not ignore spaces on the web page when comparing with words in my 'blacklist'.
(Unless I am missing a setting that is. In that case 'my bad'.)
💻 Details
- OS: Windows 10
- Browser: Firefox
- Browser Version: 102.0
- Affected site(s): All websites.
Hi @JamieRCHI,
Could you share what options you have for the word in question? The only way I was able to re-create the situation you describe was if I had both Partial match method, and match separators turned on like this:
If that is your case as well, it is working as expected, and you would either need to change one of those options (I'd probably recommend match separators, but either should work.
Thanks. That was it.
Sorry for the confusion.
No worries @JamieRCHI, thanks for responding. Currently there is not a way to customize which separators or matched, and right now it includes -, _, and . It isn't always helpful, but in some cases it can be, which is why it is usually off by default. Take care!