- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 16 Jan 2014 12:38:45 -0500
- To: www-style@w3.org
On 1/16/14 12:30 PM, Marat Tanalin wrote: > 2. if FIELSET has any `display` value different from `native`, then the FIELSET and its LEGEND are rendered as regular (like DIV) elements, without any special styling; That's not web-compatible, unfortunately. Tons of websites out there style fieldsets as "inline" or "block" and expect them to keep looking like fieldsets. If only we'd set this up to start with... > 3. if LEGEND only (with FIELDSET's default styles untouched) has any `display` value different from `native`, then the LEGEND only is rendered as regular (like DIV) element (without any special styling): entirely inside FIELDSET, without any implicit styling like top offset of half-line height. This may have the same issue. See the discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=653870 Note that there are proposals to use a new _property_ like "binding" or "appearance" to do what you're suggesting, though. Those are much more likely to be fruitful, I think, than adding a magic "display" value. > As a much less universal alternative, a "quickfix" for FIELSET/LEGEND themselves could be to make them implicitly become regular elements if _any_ of CSS properties are set for FIELDSET or for any of its descendants. _Definitely_ not web compatible. > Of course, changing things now would affect backward compatibility to some extent Yes, you could say that. ;) -Boris
Received on Thursday, 16 January 2014 17:39:14 UTC