Automatically close nsfw issues

[ksy36]

We should close the issue if domain is in nsfw list or a nsfw label is added to the issue

[LurkerHub]

Why? Is FF a SFW-only browser?

[karlcow]

1. Webcompat.com is a multi-browsers project, even if Mozilla (Firefox) has the lion share here and the steward for it.
2. It's about people, not browsers. There are people working with the content, to triage and review these issues. NSFW (and this doesn't mean only adult content) issues can definitely be distressful, or even damaging for the well-being of people.

I hope it helps understand. It's not perfect, but better for us as humans.

[LurkerHub]

Thank you for the response.

Can you please clarify:

If an incompatibility is detected on a site that has NSFW content,
But the reproduction and investigation steps do not involve exposure to said context,
Can the incompatibility still be submitted?

For example, I have encountered problems on sites that host NSFW content, but in order for the content to be visible, the user has to toggle an "NSFW" switch, which pops up an "Are you over 18" dialog that has to be acknowledged before the NSFW content is shown. The site is technically NSFW, but the issue happens on the "SFW path" as well and exposure to NSFW content requires deliberate actions by the user.

Thank you.

[karlcow]

if you are able to reduce it and create a test case reproducing the issue that would be great.

[LurkerHub]

Already did (no humans were harmed in the process).

So I assume the answer to my question is "yes".

Now to the more problematic scenario: if there is a compatibility issue on NSFW content, and no SFW testcase can be easily found, is there an alternative way to bring it to the developers' attention?

Thank you.