[Bug 13062] HTML spec should not dictate first/last child nesting level and exact order of child siblings

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13062

--- Comment #19 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-06-27 17:41:33 UTC ---
(In reply to comment #10)
> The <legend> not being a legend is not breakage?

Oh, didn't notice that.  Yeah, we'd still have to require that <legend> be a
child of <fieldset>, but we don't have to require that it be the first child. 
But that's bug 12834.  AFAICT there are no problems with <div>s around list
items, which strikes me as the most useful suggestion here (and the only
specific one not already covered by another bug).

(In reply to comment #11)
> The bug _is_ narrow: HTML spec currently uses wrong means to describe semantic
> parent/child relations.

The bug proposes several different changes to the specification, in that
several different changes would be made to different sections.  Moreover, it
would be possible for the editor to accept some of the changes and not others:
for example, he WONTFIXed bug 12835 but left bug 12834 open for now.  There
should be separate bugs for separate requested changes (even if the *reason* is
the same) so that they can be given different resolutions if necessary.  Bugs
should be filed about what changes you want in the specification's text, not
what changes you want in its philosophy -- the latter should be used as
rationale for the former.

(In reply to comment #15)
> Considering the reasoning I've stated in comment 11, I'm renaming the bug back
> to original title since "Allow grouping list items with divs" does not reflect
> the real bug point.

I'm not going to argue further, but I advise you that I think this will hurt
your bug's chances of being accepted.

-- 
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 Monday, 27 June 2011 17:41:41 UTC