- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 29 Sep 2009 02:19:21 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7657
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2009-09-29 02:19:20 ---
Well, these two features aren't anywhere near important enough to justify a
whole new set of elements, IMHO; even introducing <details> and <figure> is
somewhat pushing it.
As far as the semantic argument, personally I don't understand the problem.
Prior to HTML5, <dt> and <dd> had meaning inside <dl> only. These elements are
meaningless outside <dl>, so why can't we introduce new meaning to these
elements in new contexts? Furthermore, the new meanings are so close to the old
meanings, that I really don't see an issue. If you disagree, please escalate
this to the chairs.
As far as the compatibility argument, as I see it we have three options:
1. Use <dt>/<dd> and have people continue to use <div>s while we wait for 25%
of today's browsers to be replaced with the current generation of browsers.
2. Use <legend> and have people continue to use <div>s while we wait for
browsers to implement the HTML parser and for 100% of today's browsers to be
replaced with that new generation of browsers.
3. Not have these two features and have people continue to use <div>s.
Currently the spec picks 1. If you disagree, please escalate this to the
chairs.
--
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 Tuesday, 29 September 2009 02:19:32 UTC