This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#display-types Comment: It looks like at least some browsers restrict legend display values to "block" Posted from: 173.48.34.3
Specifically, Webkit and Presto seem to have: fieldset > legend { display: block !important } or some equivalent in their UA sheets. Should the spec be calling for this?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: I don't know, is there any good reason to restrict it as such? Is there any precedent in the HTML spec's rendering section to restrict a CSS property on an element in this way?
(In reply to comment #1) > Specifically, Webkit and Presto seem to have: > > fieldset > legend { display: block !important } > > or some equivalent in their UA sheets. Should the spec be calling for this? IIRC, <legend> isn't fully handled through CSS at all in most current browsers. The "equivalent" is just some magic handling of the display of the element in C++. This should hopefully *not* be enshrined in the HTML5 spec, as it is a very weird area of current browsers. Instead, we should be adding something to CSS that allows the proper display of <legend>, so browsers can remove the magic but still display legacy content as it always has.
> 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.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. Thanks for the help here.
Checked in as WHATWG revision r5602. Check-in comment: legend { display: list-item } should no longer get a bullet http://html5.org/tools/web-apps-tracker?from=5601&to=5602
That looks reasonable... dbaron, want to check it over too?