1-0 branch, Infinity-loader's `destroyOnInfinity` does not seem to work
See original GitHub issueHi!
I am not positive, but the destroyOnInfinity
property available on the infinity-loader
no longer seems to work.
I can confirm that this line is called. But the element stays in the DOM… nothing happens. If you add the destroyOnInfinity
to the dummy app, the element never goes away. I can write a failing test for it if you need.
Since everyone is pushing on a 1-0 release, it might make sense to instead toggle the isVisisble
attribute on the component? I am not sure that components are supposed to be destroying themselves…
Easy workaround, Add this to your CSS:
.infinity-loader.reached-infinity {
display: none !important;
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
ember-infinity/README.md at master - GitHub
The infinity-loader component as some extra options to make working with it easy! It is based on the IntersectionObserver API. In essence, instead...
Read more >inactive component - OSCHINA - 中文开源技术交流社区
inactive transaction branch等待事件是由于dblink连接超时导致的,当多个dblink同时连接远程数据库做相同的工作时,等待的dblink如果等待时间过长就会触发此等待事件。
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Totally. I will PR into the 1-0 branch and add some notes to the readme for upgrading.
@Duder-onomy ah that might be even better! Awesome idea 👍 Could add to #242 but still waiting for an upstream PR into ember-in-viewport 😦 . It might be sitting there for a while, so maybe you/I could do a PR into the 1-0 branch instead.