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 -
Replying to @wycats @slightlylate
Were you thinking of using it for getting data from a set, recycling elements, or both?
1 reply 0 retweets 0 likes -
Replying to @aerotwist @slightlylate
as a (drop in) alternative for scroll handlers, no?
1 reply 0 retweets 0 likes -
it's not actually that good for that :/
1 reply 0 retweets 0 likes -
Replying to @Runspired @wycats and
it's timing and the data it provides are both insufficient. surprising given what it was billed for.
2 replies 0 retweets 0 likes -
say you’re loading comments or pulling data from a set, then it’s ideal imo.
1 reply 0 retweets 0 likes -
not if you want to load before the user reaches the bottom.
1 reply 0 retweets 0 likes -
you’d put your marker higher up the page, not at the bottom. Or use requestIdleCallback.
1 reply 0 retweets 1 like -
so you'd use hacks. we can do better than IO today for all use cases IO has.
2 replies 0 retweets 0 likes
"better than IO today" means IO is implemented poorly, not that we need a guaranteed hi-fi API.
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.