{"id":42,"date":"2006-01-22T10:36:02","date_gmt":"2006-01-22T17:36:02","guid":{"rendered":"https:\/\/steve.ganz.name\/write\/?p=42"},"modified":"2006-04-23T18:02:40","modified_gmt":"2006-04-24T01:02:40","slug":"parent_selectors_and_reverse_i","status":"publish","type":"post","link":"https:\/\/steveganz.org\/blog\/2006\/01\/parent_selectors_and_reverse_i.html","title":{"rendered":"Parent Selectors and Reverse Inheritance"},"content":{"rendered":"<p>Andy Budd asks for parent selectors in &#8220;<a href=\"http:\/\/www.andybudd.com\/archives\/2006\/01\/what_i_want_from_css3_part_2\/\">What I Want From CSS3 &#8211; Part 2<\/a>&#8220;.<\/p>\n<p>If you&#8217;re an exprienced CSS author, there is no doubt you have had a few &#8220;if only&#8221; moments when you&#8217;ve needed to affect a parent based on its children. You&#8217;re not alone. It looks like people have been <a href=\"http:\/\/www.w3.org\/Printing\/minutes960425.html\">asking for reverse inheritance since the dawn of CSS<\/a>. In the comments of Andy&#8217;s post <a href=\"http:\/\/www.mikeindustries.com\/blog\">Mike Davidson<\/a> mentions it&#8217;s been a problem for <a href=\"http:\/\/www.w3.org\/Style\/CSS\/current-work\">CSS Working Groups<\/a> <a href=\"http:\/\/www.hixie.ch\/specs\/css\/wwwstyle\/#selectors\">in the past<\/a>. Indeed, <a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-style\/1999Dec\/0007.html\">I came to find the debate is long-standing<\/a>.<\/p>\n<p>At its core, we have to remember,  the C in CSS stands for Cascade. So it stands to reason why there would be so much push-back on something that is inherently opposite. Still, if we were to go <del>down<\/del> <ins>up<\/ins> this path, an interesting question in my mind is how would you deal with specificity in this case. For instance&#8230;<\/p>\n<pre><code>a &gt; b\r\nb &lt; c<\/code><\/pre>\n<p>Who would win? Once you start asking these questions, you get more questions and you find that <a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-style\/2004Mar\/0192.html\">the answers aren&#8217;t as simple is they might seem<\/a>. The more you dig, the easier it is to see why <a href=\"http:\/\/archivist.incutio.com\/viewlist\/css-discuss\/42942\">parent selectors are a problem for implementors<\/a> and why we&#8217;re still asking for them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Andy Budd asks for parent selectors in &#8220;What I Want From CSS3 &#8211; Part 2&#8220;. If you&#8217;re an exprienced CSS author, there is no doubt you have had a few &#8220;if only&#8221; moments when you&#8217;ve needed to affect a parent based on its children. You&#8217;re not alone. It looks like people have been asking for [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-42","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts\/42","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/comments?post=42"}],"version-history":[{"count":0,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts\/42\/revisions"}],"wp:attachment":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/media?parent=42"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/categories?post=42"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/tags?post=42"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}