W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2009

[Bug 6999] Adding tag <NSFW>

From: <bugzilla@wiggum.w3.org>
Date: Fri, 12 Jun 2009 19:08:11 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MFC6l-00053q-Co@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6999


Oscar Godson <oscargodson@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oscargodson@gmail.com




--- Comment #3 from Oscar Godson <oscargodson@gmail.com>  2009-06-12 19:08:11 ---
This is not a good idea at all. It's a nice concept but for a valid HTML tag,
not so good.

1. NSFW is an opinion & why would it be not safe for work, but it'd be safe for
at home? A picture of a naked lady is not going to go over well at home either
for many people. The name would need to be changed as it doesn't actually make
sense semantically.

2. Hiding content should be left to CSS only. If not, this can and will be
abused beyond belief.

3. Why would we add NSFW if we haven't added or even thought about
<lol>,<lmao>,<wtf> or <oh>. NSFW is Internet slang along with those.

I'm not opposed to the idea of marking content, but it should be done in a
semantic way such as using attributes.

For example, <div content="pornographic"> or <img content="violent">, or even
<a content="language">


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 12 June 2009 19:08:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 June 2009 19:08:17 GMT