It's a reference indirection going through an IDREF type:
* It finds whatever elements are before the operator
* It gets the value of the operator's attribute (or type IDREF), ~ storing it in $ID
* it combines the selector after it with the root being extended with `[id=$ID]`
`/if/` would get the value of the attribute `if` and try to find an element with that value as its id.
body > div:if(body > ul > li:only-child) { background:green } body > div:not(body > ul > li:only-child) { background:green }
which may or may not already work in CSS3.
Issue here is that you're talking about this using syntax for something which has absolutely no relation. Which is a tad confusing.
No, what you want does not work in CSS, you can't make a selector conditional on a second completely unrelated selector (you probably can in XPath, although I'm sure your colleagues will soon look to end your life if you do)
div.status > span:on(div.clickme > a:hover) { display:block; }
Why would that be bad?
It's "action at a distance", it's very, very hard to understand and debug what happens.
Again, insteat of being able to just select a parent on the existence of a child, why not be able to select any element on the existence of another element? Change the background of a body > div if there is only one child in a list body > ul > li:only-child for example.
body > div /if/ body > ul > li:only-child { background:green; }
Or replace /if/ with :: or $ or whatever.