[Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=12834

--- Comment #26 from Marat Tanalin | tanalin.com <mtanalin@yandex.ru> 2011-12-05 17:34:35 UTC ---
(In reply to comment #25)
> Here's what I need to be able to evaluate the proposal in this bug:
> 
> > Please provide a complete example showing what result you want, and how you
> > cannot achieve it currently without doing what you propose. This means you need
> > to include all the CSS, scripts, markup, images, whatever, that are necessary
> > to demonstrate the problem.
> 
> These test cases are not it. They do not show the rendering you would like,
> they just do things that are currently invalid and claim that the result is
> more interoperable than some hypothetical other rendering without explaining
> what the rendering should be, what the browsers do now, etc.

How can I show desired result using something that don't allow to achieve this
desired result? 

The testcases shows exactly "the rendering I would like". If they currently are
formally invalid, this does not make rendering wrong or unclear. What exactly
don't you understand in the testcases (if any)?

> Note that if your use case is "I want more styling control over <legend>", then
> the right place to ask for that is the CSS working group. (And it's being
> worked on already.)

Quoting myself from comment 20:

CSS currently cannot generate wrappers. On the contrary, we can easily add
wrappers in HTML _right now_. So some potential fixing of CSS in some potential
future is not an equivalent option.

-- 
Configure bugmail: https://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, 5 December 2011 17:34:41 UTC