Hrmmm...this should use Intersection Observers. No data provided but dismissed?
/cc @aerotwisthttps://twitter.com/openwebdaily/status/751362746877304832 …
-
-
Replying to @slightlylate @aerotwist
yeah I expected us to use IO in ember-collection, which is our recycling scroller.
2 replies 0 retweets 0 likes -
Last I asked
@DasSurma he thought IntersectionObserver would be too high latency for infinite scroller.2 replies 0 retweets 0 likes -
Replying to @wanderview @wycats and
Right, I think this is a case of efficiency vs fidelity. IO is efficient, CW is high fidelity.
1 reply 0 retweets 1 like -
Replying to @aerotwist @wanderview and
it may be high fidelity, but getting the jank under control may be impossible.
1 reply 0 retweets 1 like -
Replying to @wycats @aerotwist and
IO is the right tradeoff of expressiveness and jank imo.
2 replies 0 retweets 0 likes -
-
Replying to @aerotwist @wanderview and
the intent of IO is to give you enough callbacks to do what you need, but not too many.
1 reply 0 retweets 0 likes -
Replying to @wycats @aerotwist and
placeholder boxes are preferable to jank. if IO isn't firing enough, I'd say browser bug
1 reply 0 retweets 0 likes
IO should be the general-purpose tradeoff, and browsers should handle the "it depends" issue
-
-
Replying to @wycats @wanderview and
you can’t get placeholder boxes recycled if you don’t know they’re needed; reqs per-frame update
2 replies 0 retweets 1 like -
: again, try IO, you'll find that if your "skirt" is built right, it'll work well for this. TEST!!!
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.