Re: [css-d] sibling + child combinator

2011-11-15 Thread Tim White
On Mon, Nov 14, 2011 at 8:46 PM, Paceaux wrote: > thank you, Philippe. That answers my question. > > I was "hoping" that the combinator could go upward in the document tree, but > my experiments with that weren't working.    It was an off-the-wall bet that > I could change styles based on whethe

Re: [css-d] sibling + child combinator

2011-11-14 Thread Paceaux
thank you, Philippe. That answers my question. I was "hoping" that the combinator could go upward in the document tree, but my experiments with that weren't working.It was an off-the-wall bet that I could change styles based on whether another element were present in a neighboring document

Re: [css-d] sibling + child combinator

2011-11-14 Thread Philippe Wittenbergh
On Nov 15, 2011, at 5:09 AM, Paceaux wrote: > 1. Does the non-adjacent sibling combinator ( ~ )only go in one directIon? > If I attempt .address ~ .newsletter, I can successfully style > newsletter. > I I try .newsletter ~ .address, I cannot style newsletter This combinator only

Re: [css-d] sibling + child combinator

2011-11-14 Thread David Laakso
On 11/14/11 3:09 PM, Paceaux wrote: I have an an element called "address" which needs a zero margin if the ul "nav_social" is present. If "nav_social" is not present, then "address" needs a 14px margin. Frank M Taylor Point the list to the problem page [s

[css-d] sibling + child combinator

2011-11-14 Thread Paceaux
I have a unique challenge with a client. I have an an element called "address" which needs a zero margin if the ul "nav_social" is present. If "nav_social" is not present, then "address" needs a 14px margin. My challenge is that "nav_social" is not a sibling of the same element as "address". Th