W3C home > Mailing lists > Public > www-style@w3.org > December 2016

Re: [css3-selectors]: Proposal: :in-view() selector for better visibility control

From: Alexander Shpack <shadowkin@gmail.com>
Date: Tue, 6 Dec 2016 20:40:54 +0200
Message-ID: <CAK4xKXnhwbKo9ETKP=S-iCNYf1mECqfmJhkuH=t_4MGHqgEwNA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Andrea Rendine <master.skywalker.88@gmail.com>, www-style <www-style@w3.org>
>
>
> This is the solution that everybody reaches for when they're
> suggesting something circular, and unfortunately, it doesn't work. ^_^
>

> Not applying any other styles would in most cases totally break the
> page's styling.


Wait, wait. It's not a "not applying". It sounds more like work with a
current snapshot, not with a live DOM tree. Don't return the result of
style applying to the source list for the selector. Like a versioning in
RDBMS on selects.



> You can't even just limit it to the elements getting
> styled by that rule, as their sizes/positions can be affected by other
> elements on the page.  It also breaks the fundamental model of CSS,
> that it's a declarative model and ordering has almost no effect.
>
> ~TJ
>

:hover can produce loop and it's ok. My proposal can produce the same loops
and it's bad. No, bad is not enough, it's BAD.

Guys, let's take away from your heads browser development mind and look on
the problem as a web developers. We would like to control elements that are
located somewhere in or out of viewport. Popup has flown out of viewport? I
would like to return it back and make it fully visible without scrolling.
Animation should start when box appears on viewport? Easy! So, how can I do
it without JS? No way. I must to be tormented... Possible loops? I don't
care. I can shot my leg in thousand ways. So what? Millions of developers
will kiss you for this feature. :)

-- 
s0rr0w
Received on Tuesday, 6 December 2016 18:42:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 December 2016 18:42:15 UTC