- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 20 Jul 2015 11:03:05 -0700
- To: Marat Tanalin <mtanalin@yandex.ru>
- Cc: Ms2ger <ms2ger@gmail.com>, Aaron Reisman <aaron@hired.com>, "www-style@w3.org" <www-style@w3.org>
On Mon, Jul 20, 2015 at 10:38 AM, Marat Tanalin <mtanalin@yandex.ru> wrote:
> 20.07.2015, 19:17, "Ms2ger" <ms2ger@gmail.com>:
>> On 07/10/2015 11:24 AM, Aaron Reisman wrote:
>>> when I say :first-child, or :last-child
>>>
>>> what I'm really saying is I want the ":first-visible-child" or the
>>> ":last-visible-child"
>>
>> what happens if I write
>>
>> :first-visible-child {
>> display: none;
>> }
>>
>> or
>>
>> :first-child:not(:first-visible-child) {
>> display: block;
>> }
>>
>> ?
>
> Error message like "CSS loop detected" in console, the loop-causing rule ignored.
Browsers (rightly) are not willing to do cycle checking in the middle
of style resolution, let alone rerun selector matching in the middle
of style resolution. Such a thing would tank performance *so bad* and
there's no real way to engineer around that.
~TJ
Received on Monday, 20 July 2015 18:03:51 UTC