There are chances of glitches in Chrome / Chromium 31, Opera 18: selectors like nth-last-child may not work correctly

In issues of chromium over the past few days, several issue has appeared, which describes approximately the following scenario: a heavy css3 selector is used, resulting in incorrect handling. In particular, the selector for several objects may not work correctly, separated by commas (#a, #b, #c etc.), nth-last-child clearly works incorrectly. Guaranteed to identify a bug with it.
The problem, apparently, is in the css query mechanism, since document.querySelector is also incorrectly addressed. What's most unpleasant - jQuery also relies on native functions (if they exist). Thus, complex jQuery queries also stopped working correctly.
If nth-last-child is used in your projects, details of the bug under the cut

The bug appears under all OS: reports in the chrome repository go under windows, we ran into a problem in Mac OS.
In version 31, as it turned out, a very strange behavior appeared
: nth-last-child:: nth-last-child (1) ==: last-child, it is possible that this is about query optimizations.
: nth-last-child (2) == null
: nth-last-child (3) ==: nth-child (1)
: nth-last-child (4) ==: nth-child (2)
and so Further.
Moreover, this behavior is included with any change in style. It can be: hover, and jQuery initialization.

Subjectively, the sensations suggest that other "heavy" css3 selectors may also not work out correctly.

In our case, immediately after detection, we checked all the projects and found $ (': nth-last-child (3)') in two pieces of code. Fortunately, the selector affected the functionality slightly. In other projects, such selectors are also sometimes found (both in styles and in code), so be prepared for a little unusual work of sites, and the more complex the site, the more likely it will be strange behavior in the most popular browser in the world that automatically updates at least in the next few days.
Yes, it seems to be one of Chrome’s usual bugs, but the trouble is that using nth-last-child as a crutch in some projects is, unfortunately, a relatively common practice, but, for example, a solution with conditional block widths for headers has appeared two years ago.

Examples of incorrect behavior:

A slightly modified code from one of the examples:
http://codepen.io/anon/pen/buDsp
To start a glitch, move the mouse in circles.
Gif with what happens: (just a hover, not clicks)


In this case, nth-of-type and nth-last-of-type works correctly, so in most cases you can use them as a temporary solution.
Oh yes, the issue, of course, is already in the chromium tracker, as it was written at the very beginning, this is just information for those who use nth-last-child in production - that this selector is likely to work incorrectly.