Visitors will be able to configure their browsers to block display of just the content enclosed by the flagged block-level element. This isn't about censorship.
That's an example of trolling to start a semantic argument - is self-censorship still censorship? - to distract people from how bad the idea is.
A not-safe-for-work warning, like a spoiler warning in a film review, should be visible in the page and implemented the same way. CSS makes clear that the separation of markup and content is a good thing, and a tag that has a moral meaning rather than a practical meaning goes completely against that.
Not-safe-for-work is a subjective value judgement, if it was going to work at all as a tag it would need much finer granularity than just on or off, for instance
<nsfw content="boobies, nuns">
and it would have to be implemented not directly in the page code, but as a service that takes its rating from a third-party trusted reviewer, and there are already "net safe" services that do that.
Slashdot Mirror
A not-safe-for-work warning, like a spoiler warning in a film review, should be visible in the page and implemented the same way. CSS makes clear that the separation of markup and content is a good thing, and a tag that has a moral meaning rather than a practical meaning goes completely against that.
Not-safe-for-work is a subjective value judgement, if it was going to work at all as a tag it would need much finer granularity than just on or off, for instance and it would have to be implemented not directly in the page code, but as a service that takes its rating from a third-party trusted reviewer, and there are already "net safe" services that do that.