- From: Christoph Päper <christoph.paeper@crissov.de>
- Date: Thu, 29 Sep 2016 09:33:35 +0200
- To: CSS public list <www-style@w3.org>
fantasai <fantasai.lists@inkedblade.net>: > > While I totally agree with you on this, I believe this is a bug in HTML and not > in CSS. The wrapper element is useful for much more than just styling: it allows > anchors to target the term-definition set, and JS to operate on it as a single > element. > > (Also from a practical point of view, I get the impression from implementers that > it is much easier to implement parsing of a new HTML element than to implement a > new CSS pseudo-class that warps the element tree, so if one of your motivations > for trying to solve the problem in CSS instead of HTML is speed-to-market... > you're targetting the wrong place. ;) You’d need to convince Hixie et al., though. <https://wiki.whatwg.org/wiki/Rationale#Why_isn.E2.80.99t_there_a_grouping-type_element_for_description_lists_to_represent_individual_name-value_groups_.28e.g..2C_a_.E2.80.9Cdli.E2.80.9D_element.29.3F_It_would_make_styling_as_well_as_adding_microdata_to_individual_groups_much_easier..5B32.5D> <https://wiki.whatwg.org/wiki/FAQ#HTML_should_group_.3Cdt.3Es_and_.3Cdd.3Es_together_in_.3Cdi.3Es.21> This FAQ says: > This is a styling problem and should be fixed in CSS. There's no reason to add a grouping element to HTML, as the semantics are already unambiguous.
Received on Thursday, 29 September 2016 07:34:08 UTC