Rule "Selectors should be known" behaving erratically

CSS rule “Selectors should be known”.

Code:
10 *:first-child+html .tables th.table_header,
11 *:first-child+html .tables th.table_header first {
12 border-right:.07em solid #888;
13 border-left:.07em solid #FFF;
14 border-bottom: 0.07em solid #888888;
15 }
16 * html .tables .tables th.table_header first,

Rule raises issue in line 10, with comment «Unexpected unknown type selector “first”».
Raises no issue in line 11.
Raises issue in line 16, again with comment «Unexpected unknown type selector “first”».

My view:
In line 10, false-positive, for “first-child” is a known pseudo-class selector.
In line 11 , again “first-child”, yet no false-positive, as before. On the other hand, a false-negative, with “first”, which is not a known selector.
In line 16, a true-positive, with “first”, which is not a known selector.
Developer may have meant the non-standard jQuery selector “:first”

Hey @duarte.fusco, which product/version (SonarQube Server XXXX.X, SonarQube Cloud, SonarQube for IDE…) are you using?