Some pseudo-classes behave inconsistently when required arguments are missing.
Examples:
:lang throws Cannot read properties of null (reading 'split')
:icontains throws Cannot read properties of null (reading 'toLowerCase')
:nth-child throws Cannot read properties of null (reading 'match')
:has / :not without arguments can report Unknown pseudo-class instead of a clear arity error
Expected:
- Invalid selectors should fail with consistent selector-validation errors (for example, "requires an argument"), not internal null/property errors or misleading unknown-pseudo errors.
This seems to come from uneven argument validation across pseudo execution paths.
Some pseudo-classes behave inconsistently when required arguments are missing.
Examples:
:langthrowsCannot read properties of null (reading 'split'):icontainsthrowsCannot read properties of null (reading 'toLowerCase'):nth-childthrowsCannot read properties of null (reading 'match'):has/:notwithout arguments can reportUnknown pseudo-classinstead of a clear arity errorExpected:
This seems to come from uneven argument validation across pseudo execution paths.