Just to report a bug in parsing a CSS3 :has selector:



Gives an error on the + sign, but the selector is perfectly fine and works properly.

Also, another bug with the :has selector:



gives a non existent error on [ square bracket.

Another one:



On the dot . .

Another one like the second, on the plus sign:

[quote="ShoresOfNowhere"]Just to report a bug in parsing a CSS3 :has selector:



Gives an error on the + sign, but the selector is perfectly fine and works properly.[/quote]

Version 21 build 21024 now gives the error on the . of .prevnextrec

[quote="ShoresOfNowhere"]Also, another bug with the :has selector:



gives a non existent error on [ square bracket.[/quote]

Bug still present in v21 build 21024

[quote="ShoresOfNowhere"]Another one:



On the dot . .[/quote]
Still present on v21 build 21024

[quote="ShoresOfNowhere"]Another one like the second, on the plus sign:

[/quote]

On v21 build 21024 the error has moved on the . of .testaco, but still it's not correct.

Thank you for the reports! First, let me clarify—this isn’t exactly “CSS3.” There’s no CSS3 standard anymore. CSS is an evolving technology with no fixed releases or baselines, and variations appear constantly, making it nearly impossible to track everything. That said, if you’re a customer, it’s best to file bugs as official reports. The forum is mainly for discussions. While I can gather issues from posts like this, there’s a chance I might miss something. Bug reports, on the other hand, are converted into tickets, which makes them much easier to track and manage.