Comments on: General sibling

By: John

John — Tue, 26 Jan 2016 23:55:25 +0000

Agreed. I had the same issue. Any idea when this can be fixed?

By: Ralph

Ralph — Fri, 25 Dec 2015 21:14:02 +0000

In reply to Mihaly. I find Chrome on iOS behaves weird in a lot of things. Getting stuff right in Chrome on iOS compared to Chrome on Android is a huge difference.

By: Mihaly

Mihaly — Thu, 19 Nov 2015 10:32:21 +0000

Just a note.
The WebKit quirk is back on Chrome in iOS9 where you can’t use general sibling combinator with pseudo selectors. Hopefully they fix it soon.

By: John Smith

John Smith — Tue, 10 Nov 2015 17:42:29 +0000

In reply to blackhat. You nailed it. Clean and concise. 10/10 Gold star. Pat on the back.

By: Matthew Lymer

Matthew Lymer — Wed, 14 Oct 2015 14:49:16 +0000

If people still don't understand, a "sibling" element (b) of another element (a) is such that is comes (b) comes after (a) and has the dame direct parent as (a), i.e.

<div>
    <span class="a"></span>
    <span class="b"></span>
    <span class="a"></span>
    <span class="a"></span>
</div>

In the above, the selector .b ~ .a selects all .a such that .a comes after a .b and shares the same direct parent of .a - so only the last 2 .a element would be selected in this example.

By: blackhat

blackhat — Thu, 23 Apr 2015 12:21:30 +0000

For those whom didn’t understand this selector, try this example:
http://codepen.io/anon/pen/jPOxOa

By: Rohit

Rohit — Thu, 27 Jun 2013 10:25:57 +0000

Give an example to understand this trick…

By: JoeShmoe

JoeShmoe — Mon, 11 Mar 2013 14:17:44 +0000

“still would select spans that are defendants descendants of whatever”

By: selvy

selvy — Sun, 18 Nov 2012 17:26:51 +0000

im little difficult to understand this trick,