- From: <bugzilla@jessica.w3.org>
- Date: Tue, 28 Sep 2010 07:28:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10546
Boris Zbarsky <bzbarsky@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NEEDSINFO |
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
--- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> 2010-09-27 17:16:21 UTC ---
> Is there any precedent in the HTML spec's rendering section to restrict a CSS
> property on an element in this way?
Well, since the HTML spec describes rendering of legends in a way that's not
expressible with CSS... it's already in this territory.
Note that this matters for web compat; for example if legends are allowed to
have display other than "block" then first-letter and first-line would not work
on them with those other display values... or would they? There may well be
sites that rely on that behavior (we certainly got bug reports about it in
Gecko, which is why I raised the bug).
As things stand, implementing a web-compatible <legend> by reference to the
HTML5 spec and the CSS2.1 spec is impossible as far as I can see. I can
guarantee that sites are styling <legend> with display:inline and expecting the
"default" legend behavior...
Note, btw, that a legend with display:block uses shrink-wrap sizing; I don't
believe the current spec specifies that either.
--
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, 28 September 2010 07:42:21 UTC