- From: Mark Brown <mark@mercurylang.org>
- Date: Tue, 6 Dec 2016 11:58:23 +1100
- To: Alexander Shpack <shadowkin@gmail.com>
- Cc: www-style <www-style@w3.org>
On Tue, Dec 6, 2016 at 10:57 AM, Alexander Shpack <shadowkin@gmail.com> wrote: > On Tue, Dec 6, 2016 at 1:04 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> This proposal, unfortunately, causes loops in precisely the same way >> that :hover can cause loops, and browsers are loathe to repeat those >> issues. >> >> ~TJ > > > I've suggested the fast solution before. > > Let's describe the definitions: > 1. Frame - statement when browser has finished scrolling tick or layout > rearrangement > 2. In-view Statement - one of the following statements (ordered): all, > partial, none, not none, not all, not partial > > For each of in-view statements select elements and apply css rules once per > frame. Even if this concept of frames were to be accepted, you have only defined the behaviour of frame N+1 in terms of frame N. The case of N=1 is still not well-defined. (What should print media do, for example?) > > So, that's all. No loops :) Unfortunately, your definition for this selector is still circular. Mark
Received on Tuesday, 6 December 2016 00:59:04 UTC